CVE-2026-94386: Use of Cache Containing Sensitive Information vulnerability in Apache Camel Oauth component
Affects camel-oauthSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium : upgrade to 4.22.2 when convenient.
Data as of 26 Oct 2026, 16:35 UTC
- Patch
- Available – fixed in 4.22.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation 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.
What to do
Upgrade org.apache.camel/camel-oauth to 4.22.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.apache.camel/camel-oauthpkg:maven/org.apache.camel/camel-oauthOther threats | Affected
| Fixed in
|
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 4.22.2 where the issue is fixed. For deployments unable to upgrade immediately, disable token caching on each OAuth profile that shares a token endpoint and client ID with another profile by setting camel.oauth.NAME.cache-tokens=false or camel.oauth.cache-tokens=false. Alternatively, configure separate clients at the identity provider for each profile requiring different scopes or client secrets to avoid shared client IDs. These mitigations ensure tokens are requested per profile configuration, preventing token sharing.
Description
A vulnerability in the Apache Camel OAuth component allows token caching to serve OAuth 2.0 bearer tokens across profiles sharing the same token endpoint and client ID but differing in scope or client secret. This can cause a profile to use a token issued for another profile's scope or client secret, potentially granting broader access than intended. The issue affects Apache Camel versions from 4.19.0 before 4.22.2. Upgrading to 4.23.0 or 4.22.2 resolves the issue. As a temporary mitigation, token caching can be disabled for affected profiles.
References
- nvd.nist.gov/vuln/detail/CVE-2026-94386 (opens in a new tab)
- github.com/apache/camel/pull/26681 (opens in a new tab)
- github.com/apache/camel/pull/27779 (opens in a new tab)
- camel.apache.org/security/CVE-2026-85317.html (opens in a new tab)
- camel.apache.org/security/CVE-2026-94386.html (opens in a new tab)
- issues.apache.org/jira/browse/CAMEL-24872 (opens in a new tab)