---
id: CVE-2026-85317
title: >-
  Apache Camel: Camel-HTTP OAuth2 Token Confusion via an Under-Keyed JVM-Global
  Token Cache
summary: >-
  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 i…
severity: medium
cvss: 4.8
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'
cvssSource: cna
cwe:
  - CWE-524
vendor: Apache Software Foundation
product: 'org.apache.camel:camel-http'
affected:
  - 'org.apache.camel:camel-http >= 4.0.0 < 4.18.5'
  - 'org.apache.camel:camel-http >= 4.19.0 < 4.22.1'
published: '2026-10-19'
updated: '2026-10-19'
sourceUpdated: '2026-10-19T10:43:39.184Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-85317'
references:
  - url: 'https://camel.apache.org/security/CVE-2026-85317.html'
    label: Apache Camel Security Advisory - CVE-2026-85317
  - url: 'https://issues.apache.org/jira/browse/CAMEL-24456'
    label: CAMEL-24456
  - url: 'https://github.com/apache/camel/pull/25834'
    label: >-
      Fix on main, released in 4.23.0 (commit
      4e2ddabd0392441b48ce591105851933b04b34b0)
  - url: 'https://github.com/apache/camel/pull/25937'
    label: >-
      Backport to camel-4.22.x, released in 4.22.1 (commit
      b0399b181d26cd8b136fa98b54ec8e5c283338da)
  - url: 'https://github.com/apache/camel/pull/25938'
    label: >-
      Backport to camel-4.18.x, released in 4.18.5 (commit
      e23332aec12f7ec3a841e52d1821e2a580c2fbc7)
tags:
  - cve.org
ingestedAt: '2026-10-19T12:27:23.808Z'
---

## Overview

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.

## Affected

- `org.apache.camel:camel-http >= 4.0.0 < 4.18.5`
- `org.apache.camel:camel-http >= 4.19.0 < 4.22.1`

## Remediation

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.

### Workarounds

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.