Insufficient Session Expiration Affecting org.apache.camel:camel-keycloak package, versions [4.16.0,4.18.5)[4.19.0,4.22.2)


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.24% (16th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JAVA-ORGAPACHECAMEL-21816688
  • published29 Oct 2026
  • disclosed26 Oct 2026
  • creditAndrea Cosentino

Introduced: 26 Oct 2026

NewCVE-2026-95663  (opens in a new tab)
CWE-613  (opens in a new tab)

How to fix?

Upgrade org.apache.camel:camel-keycloak to version 4.18.5, 4.22.2 or higher.

Overview

Affected versions of this package are vulnerable to Insufficient Session Expiration via the KeycloakSecurityProcessor in the camel-keycloak component. When token introspection and result caching are enabled, a caller can keep sending an access token that Camel introspected and cached while it was active after its exp time; because the processor checks only the cached result’s active status and the cache lifetime is based on insertion-time TTL, requests remain authorized with the expired token’s existing roles and permissions until the entry expires. Token introspection is not enabled by default, and this flaw grants no permissions beyond those already carried by the token.

Notes

  • The vulnerable path requires KeycloakSecurityPolicy.useTokenIntrospection=true (false by default); local JWT verification is unaffected. Result caching must also be enabled via introspectionCacheEnabled (true by default).

Workarounds

  • Set introspectionCacheEnabled=false on KeycloakSecurityPolicy so every request is checked against Keycloak’s introspection endpoint, which reports expired tokens as inactive.

CVSS Base Scores

version 4.0
version 3.1