CVE-2026-46455
CWE-613Published: July 6, 2026· Updated: Jul 8, 2026
Official Description
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.
Risk Analysis
This critical vulnerability in the Apache Camel Keycloak Component is due to insufficient session expiration validation. With a CVSS score of 9.8, this flaw allows an attacker to use expired or not-yet-valid Keycloak access tokens as valid, potentially leading to unauthorized access and full system compromise. The absence of an EPSS score means its exploitation likelihood is not yet quantified, but the maximum severity indicates extreme urgency.
No public exploit is currently known for this vulnerability. The flaw is remotely exploitable (AV:N) with low attack complexity (AC:L) and requires no privileges (PR:N), making it highly accessible to potential attackers.
To mitigate this, ensure that the KeycloakSecurityHelper.parseAndVerifyAccessToken method in Apache Camel Keycloak Component explicitly calls TokenVerifier.withDefaultChecks() to enforce token expiration and not-before claims. Implement robust session management and token validation practices across all Keycloak integrations.
Technical Analysis
CVE-2026-46455 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.
The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.
A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 9.8.
CVSS v3.1 Vector Breakdown
Affected Vendors & Products
Exploit & PoC Resources
Official Patches & Advisories
All References (2)
Quick Facts
Related CVEs (CWE-613)
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2026-46455 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts