CVE-2026-46455
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
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.
INFO
Published Date :
July 6, 2026, 9:16 a.m.
Last Modified :
Oct. 25, 2026, 3:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | CRITICAL | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
Solution
- Upgrade to Apache Camel version 4.21.0 or later.
- For 4.18.x, upgrade to 4.18.3.
- Validate token expiration claims in routes if upgrade is not immediate.
- Keep Keycloak access token lifetimes short.
Public PoC/Exploit Available at Github
CVE-2026-46455 has a 2 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-46455.
| URL | Resource |
|---|---|
| https://camel.apache.org/security/CVE-2026-46455.html | Mitigation Vendor Advisory |
| http://www.openwall.com/lists/oss-security/2026/07/05/8 | Mailing List Third Party Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-46455 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-46455
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Reproducer for CVE-2026-46455 — Apache Camel camel-keycloak missing TokenVerifier.IS_ACTIVE check (expired access tokens accepted)
Dockerfile Java
📡 PoC auto collect from GitHub. ⚠️ Be careful Malware.
security cve exploit poc vulnerability
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-46455 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-46455 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 25, 2026
Action Type Old Value New Value Added Translation Title: Apache Camel de Apache Software Foundation, Description: Vulnerabilidad de expiración de sesión insuficiente en el componente Keycloak de Apache Camel. El asistente de seguridad camel-keycloak KeycloakSecurityHelper.parseAndVerifyAccessToken construye un TokenVerifier de Keycloak usando withChecks(...) con solo la verificación de existencia de sujeto y la verificación de URL de realm (emisor). TokenVerifier.withChecks(...) de Keycloak añade a una lista de verificación inicialmente vacía - las verificaciones predeterminadas ascendentes se instalan solo cuando se llama a withDefaultChecks() - por lo que el predicado IS_ACTIVE incorporado, que valida las reclamaciones exp (expiración) y nbf (no antes) del token, nunca se aplica. Como resultado, el asistente verifica la firma, el sujeto y el emisor del token, pero no aplica la ventana de validez del token: un token de acceso que ha expirado, o aún no es válido, se acepta como válido. Las rutas que dependen de este asistente para autenticar solicitudes entrantes, por lo tanto, aceptan tokens de acceso que están fuera de su vida útil prevista. Este problema afecta a Apache Camel: desde 4.18.0 antes de 4.18.3, desde 4.19.0 antes de 4.21.0. Se recomienda a los usuarios actualizar a la versión 4.21.0, que corrige el problema. Si los usuarios están en la rama de versiones 4.18.x, se sugiere que actualicen a 4.18.3. La corrección hace que KeycloakSecurityHelper.parseAndVerifyAccessToken incluya la verificación TokenVerifier.IS_ACTIVE para que los tokens de acceso caducados o aún no válidos sean rechazados, alineando el asistente con el conjunto de verificaciones predeterminado de Keycloak. Para implementaciones que no pueden actualizarse inmediatamente, aplique la expiración del token fuera del asistente - por ejemplo, valide las reclamaciones exp/nbf del token de acceso en la ruta antes de confiar en él, mantenga cortas las vidas útiles de los tokens de acceso de Keycloak, y asegúrese de que cualquier puerta de enlace ascendente o servidor de recursos también valide la ventana de validez del token. -
Initial Analysis by [email protected]
Jul. 08, 2026
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:* versions from (including) 4.19.0 up to (excluding) 4.21.0 *cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:* versions from (including) 4.18.0 up to (excluding) 4.18.3 Added Reference Type Apache Software Foundation: https://camel.apache.org/security/CVE-2026-46455.html Types: Mitigation, Vendor Advisory Added Reference Type CVE: http://www.openwall.com/lists/oss-security/2026/07/05/8 Types: Mailing List, Third Party Advisory -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jul. 06, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Added SSVC {'id': 'CVE-2026-46455', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'yes'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-07-06T19:29:09.924590Z'} -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Jul. 06, 2026
Action Type Old Value New Value Added Reference http://www.openwall.com/lists/oss-security/2026/07/05/8 -
New CVE Received by [email protected]
Jul. 06, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'Apache Software Foundation', 'product': 'Apache Camel', 'versions': [{'status': 'affected', 'version': '4.18.0', 'lessThan': '4.18.3', 'versionType': 'semver'}, {'status': 'affected', 'version': '4.19.0', 'lessThan': '4.21.0', 'versionType': 'semver'}], 'packageName': 'org.apache.camel:camel-keycloak', 'collectionURL': 'https://repo.maven.apache.org/maven2', 'defaultStatus': 'unaffected'}] Added 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. Added CWE CWE-613 Added Reference https://camel.apache.org/security/CVE-2026-46455.html