CVE-2026-94386
Apache Camel: Camel-OAuth Cross-Scope Token Reuse via an Under-Keyed JVM-Global Client Credentials Token Cache
02 Description
Apache Camel: Camel-OAuth Cross-Scope Token Reuse via an Under-Keyed JVM-Global Client Credentials Token Cache
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.34% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 27.8% of scored records. A rank, not a probability.
- NVD base score
- 4.8 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- NVD analysis status
- Awaiting Analysis. NVD last modified this record on 2026-10-26.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-26 14:46Z2 DAYS AGO
- Last updated
- 2026-10-26 15:35Z2 DAYS AGO
- Reserved
- 2026-09-21
- Assigning CNA
- apache
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 4.8)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- Weaknesses
- CWE-524Use of Cache Containing Sensitive InformationBase
- Data version
- 5.2
- Document digest
- 0b0be8269ddb783e16fe0768dda07b0f508c2f4e568bf1cdde462337859daf61
05 Affected products
06 References
- camel.apache.orgApache Camel Security Advisory - CVE-2026-94386https://camel.apache.org/security/CVE-2026-94386.html
- issues.apache.orgCAMEL-24872https://issues.apache.org/jira/browse/CAMEL-24872
- github.comFix on main, released in 4.23.0 (commit 5e896b2df24bf80ad4a78be1f8a708f71d91aa16)https://github.com/apache/camel/pull/26681
- github.comBackport to camel-4.22.x for 4.22.2 (commit b2d9957bcbcf87bd5e59992fec45231876c645ed)https://github.com/apache/camel/pull/27779
- camel.apache.orgCVE-2026-85317, the same class of defect in the camel-http OAuth2 client token cachehttps://camel.apache.org/security/CVE-2026-85317.html
07 Remediation
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.22.x stream should upgrade to 4.22.2. The 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. The token cache is now keyed on every input of the token request: the token endpoint, the client ID, a SHA-256 fingerprint of the client secret, so that the raw secret is not kept in the cache, and the requested scope, so profiles that differ in credentials or scope obtain separate tokens while equivalent profiles still share one. The 4.18.x line and earlier never carried the client credentials token resolver and are not affected.