CVE-2026-46455: Apache Camel insufficient session expiration in Keycloak component

CVE-2026-46455 · Severity: critical · CVSS 9.8 · Published 2026-07-06

Apache Camel's Keycloak authentication helper fails to validate whether access tokens have expired or not yet become valid, accepting tokens outside their intended lifetime. This allows attackers to reuse expired tokens to gain unauthorized access to Camel routes that rely on this helper for authentication, potentially leading to data breach, unauthorized operations, or service compromise.

Technologies: Apache Camel, org.apache.camel:camel-keycloak (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2026-46455 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46455 being exploited in the wild.
How severe is CVE-2026-46455?
Critical severity, with a CVSS score of 9.8, published 6 July 2026.
Which products and versions are affected?
Apache Camel 4.18.0 to 4.18.2, 4.19.0 to 4.20.x; org.apache.camel:camel-keycloak (Maven) ECOSYSTEM:introduced=4.18.0,fixed=4.18.3.
Is there a fix for CVE-2026-46455?
Yes. org.apache.camel:camel-keycloak (Maven): upgrade to 4.18.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46455 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-46455?
Check whether you run Apache Camel or org.apache.camel:camel-keycloak (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.camel:camel-keycloak (Maven): upgrade to 4.18.3 or later
    # set org.apache.camel:camel-keycloak to 4.18.3 in your pom.xml or build.gradle

Technical details

The KeycloakSecurityHelper.parseAndVerifyAccessToken method builds a Keycloak TokenVerifier using only subject-exists and realm-URL checks, but does not call withDefaultChecks(), which means the built-in IS_ACTIVE predicate (which validates exp and nbf claims) is never applied. This is a logic error in how the TokenVerifier is configured: withChecks() appends to an empty check list rather than augmenting the defaults. As a result, the helper verifies token signature, subject, and issuer but skips expiration and not-before validation. An attacker can obtain a valid token, wait for it to expire, and reuse it to authenticate to unpatched Camel routes. Network-reachable routes that depend on this helper accept the expired token without any additional privileges or user interaction required. Fix: upgrade to version 4.21.0 (or 4.18.3 for the 4.18.x stream) to include the IS_ACTIVE check in token validation.

Affected products

  • Apache Camel 4.18.0 to 4.18.2, 4.19.0 to 4.20.x

Identifiers

  • CVE-2026-46455
  • GHSA-mqwc-6qwc-v9gq

Timeline

  • 2026-07-06: disclosed
  • 2026-07-06: patched: versions 4.18.3 and 4.21.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.