Keycloak Token Verification Bypass in Apache Camel

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

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-46455 exposes a critical session management flaw in Apache Camel's Keycloak integration where the KeycloakSecurityHelper fails to enforce essential token validation checks. By only validating subject existence and realm URL while omitting the IS_ACTIVE predicate and other default checks, attackers can exploit expired, revoked, or inactive tokens to maintain unauthorized access. This vulnerability affects any organization using Apache Camel with Keycloak for authentication and authorization, potentially allowing threat actors to bypass session expiration controls and maintain persistent access to protected resources.

Casky's 283 matched skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK techniques TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using the platform would identify suspicious patterns including: tokens passing verification despite expiration status, SESSION_FIXATION attempts where old credentials remain valid indefinitely, and CREDENTIAL_REUSE indicators showing inactive accounts maintaining active sessions. The skills map specifically to token verification bypass chains, detecting when security helpers skip critical validation gates—flagging incomplete check lists in TokenVerifier configurations and missing withDefaultChecks() calls that would normally enforce token freshness and active status validation.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-46455.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

identity access management · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-46455

Casky has 283 skills that investigate the attack patterns behind CVE-2026-46455. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn