Insufficient Session Expiration vulnerability in Apache Camel Keycloak component.
Insufficient Session Expiration vulnerability in Apache Camel Keycloak component. This issue affects Apache Camel: from 4.16.0 before 4.18.5, from 4.19.0 before 4.22.2. When token introspection is enabled on the camel-keycloak KeycloakSecurityPolicy (useTokenIntrospection=true), the security processor validates the access token of a request by sending it to Keycloak's OAuth 2.0 token introspection endpoint, and accepts the token while the response reports it as active. The introspection endpoint reports a token as inactive once its exp (expiration) time has passed, so on this path the active flag is what enforces token expiry. Introspection results are cached by default (introspectionCacheEn
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Apache Software Foundation
- Product
- Apache Camel
- CVSS v3.1
- 4.8 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- Fix
- not yet available
- Weakness
- CWE-613
- Exposure class
- Identity, Web platform
- NVD status
- Received
Why it ranks 17 (Routine)
- CVSS v3.1 4.8 medium
- Exposed product class: identity
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- NIST National Vulnerability Database (CVE API 2.0) (nvd.nist.gov)
- CVE-2026-95663 on this site · NVD · CVE.org · Vulnpedia