boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-85317

Apache Camel: Camel-HTTP OAuth2 Token Confusion via an Under-Keyed JVM-Global Token Cache
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   N   H   N   N  U  L  L  N    4.8   .0052   44.8     —
AFFECTED
  Product       Versions  Fixed
  Apache Camel  4.0.0 –   4.18.5
TIMELINE
  Sep 3   Reserved by apache
  Oct 19  Published (CNA: apache)
  Nov 3   EXPLOIT PUBLISHED — CVE-2026-85317 (Apache Software Foundation Apache Camel). Public exploit reference added.
CWE-524 · CNA: apache · CVSS v3.1 · 5 references · NVD status: Analyzed

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.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
September 3, 2026ReservedReserved by apache
October 19, 2026PublishedPublished (CNA: apache)
November 3, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-85317 (Apache Software Foundation Apache Camel). Public exploit reference added.

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
Apache Software FoundationApache CamelMaven4.0.04.18.5

Weaknesses

CWE-524

References (5)

Related

Authoritative record: CVE-2026-85317 at cve.org

Vendors: apache

Weaknesses: CWE-524

Ecosystems: Maven

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-85317 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.