CVE-2026-23552
Cross-realm JWT issuer check bypass in Camel-Keycloak policy.
Is CVE-2026-23552 being exploited?
Not confirmed. CVE-2026-23552 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-23552?
CVE-2026-23552 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-23552?
Yes. A fix has been recorded for CVE-2026-23552. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-23552 affect?
CVE-2026-23552 affects Apache Camel with Keycloak integration (CamelKeycloakSecurityPolicy) 4.15.0–4.17.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-23552?
Upgrade to Camel 4.18.0; verify iss validation and tenant isolation.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows cross-realm token acceptance; attacker can bypass tenant isolation and access resources across realms by forging tokens.
Immediate action required
- affected>= 4.15.0 and < 4.18.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.