VulnerabilityPublished 26 Oct 2026

CVE-2026-95663: Apache Camel · Insufficient Session Expiration

Affects Apache CamelSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium : upgrade to 4.22.2 or 4.18.5 when convenient.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.22.2, 4.18.5

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache to 4.22.2 or 4.18.5.

Affected software

Product	Affected	Fixed in
Apache Camelorg.apache.camel:camel-keycloak	Affected >=4.19.0 <4.22.2	Fixed in 4.22.2
Apache Camelorg.apache.camel:camel-keycloak	Affected >=4.16.0 <4.18.5	Fixed in 4.18.5
MavenApache Software Foundation/org.apache.camel:camel-keycloak`pkg:maven/Apache Software Foundation/org.apache.camel:camel-keycloak`Other threats	Affected >=4.16.0 <4.18.5 >=4.19.0 <4.22.2	Fixed in 4.18.5 4.22.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Camel to version 4.23.0 or later. If upgrading immediately is not possible, users on the 4.22.x stream should upgrade to 4.22.2, and those on the 4.18.x stream should upgrade to 4.18.5. Versions 4.16.x, 4.17.x, and 4.19.x to 4.21.x are end-of-life and must be replaced with supported versions. As a temporary workaround, disable the introspection cache by setting introspectionCacheEnabled=false on the KeycloakSecurityPolicy to ensure every request is validated against the introspection endpoint, which correctly reports expired tokens as inactive. Lowering the cache TTL reduces but does not eliminate the vulnerability window.

Description

CVE-2026-95663 is an insufficient session expiration vulnerability in the Apache Camel Keycloak component affecting versions from 4.16.0 before 4.18.5 and from 4.19.0 before 4.22.2. When token introspection is enabled, the component caches token introspection results without respecting the token's expiration time, allowing expired tokens to be accepted for up to the cache's time-to-live. This can permit continued use of recently expired tokens for a short window, but does not allow token forgery or privilege escalation. The issue is fixed in Apache Camel versions 4.18.5 and 4.22.2.

Impact

The vulnerability allows a short window during which expired access tokens may still be accepted due to caching of introspection results without enforcing token expiration. This can lead to continued access with expired tokens for up to the cache TTL (default 60 seconds, possibly up to 300-600 seconds if configured). However, it does not allow attackers to forge tokens or escalate privileges beyond what the token originally granted. The impact is limited to token reuse shortly after expiration and only affects systems using token introspection with caching enabled.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:01 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats