CVE-2026-85317: Use of Cache Containing Sensitive Information vulnerability in Apache Camel HTTP component
CVE-2026-85317 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Medium
- CVSS base score
- 4.8 (Apache), 4.8 (Red Hat)
- Weakness
- CWE-524
- Fixed releases
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-85317; each belongs to its advisory, not to every product listed. How records are collected and checked.
How do I fix CVE-2026-85317?
Upgrade to a fixed release named by the vendor:
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
- Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)
Vendor advisories for CVE-2026-85317
Apache
1 advisory- Advisory severityMedium4.8
Medium [CVE-2026-85317] Use of Cache Containing Sensitive Information vulnerability in Apache Camel HTTP component
CVE-2026-85317Source published Source updated
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…
- Affected products in this advisory
- Apache Camel HTTP
- Source-reported affected versions
- 4.0.0 before 4.18.5
- 4.19.0 before 4.22.1
- Source-reported fixed versions
- 4.18.5
- 4.22.1
- Mitigation guidance
- 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.
- 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.
Red Hat
1 advisory- Advisory severityMedium4.8
Medium [CVE-2026-85317] Unauthorized access via shared OAuth2 token cache
CVE-2026-85317Source published Source updated
Unauthorized access via shared OAuth2 token cache. Red Hat rates this moderate (CVSS 4.8). Weakness: CWE-524. Affected products named by the advisory: Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4; Red Hat Fuse 7.
- Related products — impact not confirmed
- Red Hat build of Apache Camel 4 for Quarkus 3
- Red Hat build of Apache Camel for Spring Boot 4
- Red Hat Fuse 7
- Source-reported affected versions
- < 4.0.0
- < 4.18.5
- < 4.19.0
- < 4.22.1
- Source-reported fixed versions
- 4.23.0
- 4.18
- 4.18.5
- 4.22
1 more entries in the full advisory.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
References
More Apache advisories
CVE-2026-85251Oct 19, 2026Apache Camel HTTP information disclosureCVE-2026-78164Oct 19, 2026Apache Camel HTTP information disclosureCVE-2026-86336Nov 10, 2026Apache TomEE running on JDK 21 or later skips EJB method authorization checksCVE-2026-86531Nov 10, 2026The embedded OpenEJB HTTP server does not limit the size of incoming request bodiesCVE-2026-87758Nov 10, 2026The remote EJB client does not verifyCVE-2026-97849Nov 10, 2026The embedded Derby network service ignores its configured bind address and listens on all
Get an email when Apache publishes the next one.
See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Get alerts for new CVEs on your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
