Insufficient session expiration in Apache Camel
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub. Impact type from CWE-613.
Summary
Insufficient Session Expiration vulnerability in Apache Camel Keycloak Component. The camel-keycloak security helper KeycloakSecurityHelper.parseAndVerifyAccessToken builds a Keycloak TokenVerifier using withChecks(...) with only the subject-exists check and the realm-URL (issuer) check. Keycloak's TokenVerifier.withChecks(...) appends to an initially empty check list - the upstream default checks are installed only when withDefaultChecks() is called - so the built-in IS_ACTIVE predicate, which validates the token's exp (expiration) and nbf (not-before) claims, is never applied. As a result the helper verifies the token signature, subject and issuer but does not enforce the token's validity window: an access token that is expired, or not yet valid, is accepted as valid. Routes that rely on this helper to authenticate inbound requests therefore accept access tokens that are outside their intended lifetime. This issue affects Apache Camel: from 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes KeycloakSecurityHelper.parseAndVerifyAccessToken include the TokenVerifier.IS_ACTIVE check so that expired or not-yet-valid access tokens are rejected, aligning the helper with Keycloak's default check set. For deployments that cannot upgrade immediately, enforce token expiration outside the helper - for example validate the access token's exp/nbf claims in the route before trusting it, keep Keycloak access-token lifetimes short, and ensure any upstream gateway or resource server also validates the token validity window.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Apache | Apache Camel | 4.18.0 to before 4.18.3; 4.19.0 to before 4.21.0 | 4.18.3, 4.21.0 | Patch available | CNA |
| — | org.apache.camel:camel-keycloak (Maven) | 4.18.0 to before 4.18.3 | 4.18.3 | Patch available | GHSA-mqwc-6qwc-v9gq |
| — | org.apache.camel:camel-keycloak (Maven) | 4.19.0 to before 4.21.0 | 4.21.0 | Patch available | GHSA-mqwc-6qwc-v9gq |
- Apache Camel VendorApache Affected 4.18.0 to before 4.18.3; 4.19.0 to before 4.21.0 Fixed in 4.18.3, 4.21.0 Patch available CNA
- org.apache.camel:camel-keycloak (Maven) Vendor— Affected 4.18.0 to before 4.18.3 Fixed in 4.18.3 Patch available GHSA-mqwc-6qwc-v9gq
- org.apache.camel:camel-keycloak (Maven) Vendor— Affected 4.19.0 to before 4.21.0 Fixed in 4.21.0 Patch available GHSA-mqwc-6qwc-v9gq
Remediation
- Fix · CNA Apache Camel (Apache Software Foundation) Fixed in 4.18.3, 4.21.0
- Fix · GHSA-mqwc-6qwc-v9gq org.apache.camel:camel-keycloak (Maven) Fixed in 4.18.3 Advisory →
- Fix · GHSA-mqwc-6qwc-v9gq org.apache.camel:camel-keycloak (Maven) Fixed in 4.21.0 Advisory →
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Apache Camel 4.18.3, 4.21.0
3 records Highest priority Priority MEDIUM 3 MEDIUM
Other records, highest priority first
- TI-2026-31931 Deserialization of untrusted data in Apache CamelPriority MEDIUM 51
- TI-2026-34250 Deserialization of untrusted data in Apache CamelPriority MEDIUM 42
Timeline
- 2026-10-02 Threatist record created from CVE-2026-46455
- 2026-10-03 Alias added: GHSA-mqwc-6qwc-v9gq
References
Advisory 3
Other 8
- https://github.com/apache/camel/pull/23197
- https://github.com/apache/camel/pull/23204
- https://github.com/apache/camel/commit/39133b1ada37c60dea53f3b7db720dbd2ae73fa6
- https://github.com/apache/camel/commit/7f4c4736021aff4fad925eca3bf456b95db038f3
- https://github.com/apache/camel
- https://github.com/apache/camel/releases/tag/camel-4.18.3
- https://github.com/apache/camel/releases/tag/camel-4.21.0
- https://issues.apache.org/jira/browse/CAMEL-23504
More Apache Camel vulnerabilities
- TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcast CVSS 4.0CRITICAL 10.0
- TI-2026-18973 Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy CVSS 3.1CRITICAL 9.1
- TI-2026-76339 Path traversal in Apache Camel azure-files component CVSS 3.1CRITICAL 9.1
- TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directory CVSS 3.1CRITICAL 9.1
- TI-2025-20435 Apache Camel: Camel Message Header Injection via Improper Filtering CVSS 3.1MEDIUM 5.6
- TI-2026-34899 Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-46455 · CVE Program
- CVE-2026-46455 · NVD
- FIRST EPSS
- GHSA-mqwc-6qwc-v9gq · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences