Apache Software Foundation Apache Camel
Apache Camel: Camel-Keycloak: The access-token validity window is not verified because the IS_ACTIVE check is missing from the TokenVerifier, allowing expired tokens to be accepted
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.18.0, < 4.18.3
- >= 4.19.0, < 4.21.0
Fixed in 4.18.3, 4.21.0
Mitigation
Upgrade Apache Camel to 4.18.3 or 4.21.0 or later.
References
- Vendor advisory camel.apache.org/security/CVE-2026-46455.html
Timeline
Days relative to CVE publicationFirst public PoC 7.3 days after publication; not in CISA KEV. First PoC: oscerd/CVE-2026-46455 (created 13 Jul 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| oscerd/CVE-2026-46455 | 13 Jul 2026 +7.3 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
PoC characteristics
What to hunt for in your logs · from 1 PoC repoGET /exploit/attack
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/exploit/attack(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-46455 Apache Software Foundation Apache Camel exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-46455; classtype:web-application-attack; sid:9366136; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: Apache Software Foundation Apache Camel exploit attempt (CVE-2026-46455)
id: gg-pocmon-cve-2026-46455-9366136
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-46455. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-46455
logsource:
category: webserver
detection:
selection:
cs-method: GET
cs-uri-stem|contains|all:
- '/exploit/attack'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: critical
tags:
- attack.initial_access
- attack.t1190
- cve.2026.46455