Skip to main content

Camel CVE-2026-23552

CRITICAL
Origin Validation Error (CWE-346)
2026-02-23 security@apache.org GHSA-c3f3-cc42-xr9v
9.1
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

4
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
Analysis Generated
Mar 12, 2026 - 21:55 vuln.today
PoC Detected
Feb 26, 2026 - 16:46 vuln.today
Public exploit code
CVE Published
Feb 23, 2026 - 09:17 nvd
CRITICAL 9.1

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 3 maven packages depend on org.apache.camel:camel-keycloak (2 direct, 1 indirect)

Ecosystem-wide dependent count for version 4.15.0.

DescriptionCVE.org

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.

AnalysisAI

Cross-realm token acceptance bypass in Apache Camel Keycloak security policy. The KeycloakSecurityPolicy fails to properly validate token issuers, accepting tokens from different Keycloak realms. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Attacker obtains JWT token from different Keycloak realm
Exploit
Send token to target Camel endpoint
Execution
KeycloakSecurityPolicy accepts token without validating issuer claim
Impact
Access granted across realm boundary

Vulnerability AssessmentAI

Exploitation Apache Camel versions 4.15.0 through 4.17.x with KeycloakSecurityPolicy configured for multi-tenant Keycloak deployments where tokens from different realms are accessible to attacker. Additional conditions and limiting factors are described in the full assessment.
Risk Assessment CVSS 9.1. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Attacker obtains valid token from one Keycloak realm, uses it to authenticate to a Camel route protected by a different realm's security policy.
Remediation Update Apache Camel. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Identify all systems using Apache Camel with Keycloak component and assess their exposure; isolate or disable affected services if business-critical. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-23552 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy