---
title: "CVE-2026-46455: Apache 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"
url: https://erroneo.us/security/cve/CVE-2026-46455/
description: "CVE-2026-46455 (org.apache.camel:camel-keycloak (Maven)): Insufficient Session Expiration vulnerability in Apache Camel Keycloak Component. The…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-07-06
date_modified: 2026-08-28
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-46455"
kev: false
cvss: 9.8
epss: 0.0069
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-46455: Apache 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

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.7% , percentile 52: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 52% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes org.apache.camel:camel-keycloak (Maven) >= 4.18.0, < 4.18.3, fixed in 4.18.3 ; org.apache.camel:camel-keycloak (Maven) >= 4.19.0, < 4.21.0, fixed in 4.21.0 . Check your lockfile, including transitive dependencies.

## What it is

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 ISACTIVE 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.ISACTIVE 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 packages

- Maven `org.apache.camel:camel-keycloak` >= 4.18.0, < 4.18.3 → fixed: 4.18.3
- Maven `org.apache.camel:camel-keycloak` >= 4.19.0, < 4.21.0 → fixed: 4.21.0

## Affected products (CVE record)

- Apache Software Foundation Apache Camel: 4.18.0 < 4.18.3, 4.19.0 < 4.21.0

## Severity

- CISA-ADP CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.69% probability of exploitation activity in the next 30 days; percentile 52.

## Sources

- [camel.apache.org](https://camel.apache.org/security/CVE-2026-46455.html)
- [GitHub Advisory GHSA-mqwc-6qwc-v9gq](https://github.com/advisories/GHSA-mqwc-6qwc-v9gq)
- [CVE.org record CVE-2026-46455](https://www.cve.org/CVERecord?id=CVE-2026-46455)
- [NVD entry CVE-2026-46455](https://nvd.nist.gov/vuln/detail/CVE-2026-46455)
- [openwall.com](http://www.openwall.com/lists/oss-security/2026/07/05/8)
- [github.com](https://github.com/apache/camel/pull/23197)
- [github.com](https://github.com/apache/camel/pull/23204)
- [github.com](https://github.com/apache/camel/commit/39133b1ada37c60dea53f3b7db720dbd2ae73fa6)
- [github.com](https://github.com/apache/camel/commit/7f4c4736021aff4fad925eca3bf456b95db038f3)
- [github.com](https://github.com/apache/camel/releases/tag/camel-4.18.3)
- [github.com](https://github.com/apache/camel/releases/tag/camel-4.21.0)
- [issues.apache.org](https://issues.apache.org/jira/browse/CAMEL-23504)

---
Source page: https://erroneo.us/security/cve/CVE-2026-46455/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt