Security Digest · Vulnerability record

CVE-2026-23552: Apache Camel: KeycloakSecurityPolicy does not validate issuer of JWT tokens against configured realm

Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy Apache Camel Keycloak component.

CVSS 9.1 Critical EPSS 0.6% · p48

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 0.6%, percentile 48: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 48% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes org.apache.camel:camel-keycloak (Maven) >= 4.15.0, < 4.18.0, fixed in 4.18.0. Check your lockfile, including transitive dependencies.

What it is

Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy Apache Camel Keycloak component. The Camel-Keycloak KeycloakSecurityPolicy does not validate the iss (issuer) claim of JWT tokens against the configured realm. A token issued by one Keycloak realm is silently accepted by a policy configured for a completely different realm, breaking tenant isolation. This issue affects Apache Camel: from 4.15.0 before 4.18.0. Users are recommended to upgrade to version 4.18.0, which fixes the issue.

From the GitHub advisory

Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy Apache Camel Keycloak component.

The Camel-Keycloak KeycloakSecurityPolicy does not validate the iss (issuer) claim of JWT tokens against the configured realm. A token issued by one Keycloak realm is silently accepted by a policy configured for a completely different realm, breaking tenant isolation. This issue affects Apache Camel: from 4.15.0 before 4.18.0.

Users are recommended to upgrade to version 4.18.0, which fixes the issue.

Weakness type: CWE-346.

Product: org.apache.camel:camel-keycloak (Maven) · Assigned by: apache · Published: 2026-02-23

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Mavenorg.apache.camel:camel-keycloak>= 4.15.0, < 4.18.04.18.0
VendorProductAffected versions (per CVE record)
Apache Software FoundationApache Camel4.15.0 < 4.18.0

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.19.1 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub3.19.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 0.61% probability of exploitation activity in the next 30 days; percentile 48.

Timeline

  • — CVE record last updated
  • — CVE record published by apache
  • — GitHub-reviewed advisory GHSA-c3f3-cc42-xr9v published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. camel.apache.org camel.apache.org

Vulnerability records

  1. GitHub Advisory GHSA-c3f3-cc42-xr9v github.com
  2. CVE.org record CVE-2026-23552 cve.org
  3. NVD entry CVE-2026-23552 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. openwall.com openwall.com
  3. github.com github.com
  4. issues.apache.org issues.apache.org

Critical Maven advisories · Today’s Security Digest