Use of Cache Containing Sensitive Information Affecting org.apache.camel:camel-http package, versions [4.0.0,4.18.5)[4.19.0,4.22.1)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHECAMEL-21429384
- published22 Oct 2026
- disclosed19 Oct 2026
- creditClaude Security
Introduced: 19 Oct 2026
NewCVE-2026-85317 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-http to version 4.18.5, 4.22.1 or higher.
Overview
org.apache.camel:camel-http is a versatile open-source integration framework based on known Enterprise Integration Patterns.
Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via the OAuth2 token cache in the camel-http component. The JVM-wide cache keys tokens by request URI and client credentials, so when multiple routes share those values but differ in scope, resource indicator, or token endpoint, a token minted for one configuration can be used by another. An attacker who can invoke such a route can trigger an outbound request carrying a token with broader authority than configured or one issued by a different authorization server; this requires those distinct OAuth2 configurations to run in the same JVM.
Workarounds
- Run endpoints that differ in scope, resource indicator, or token endpoint in separate JVMs to prevent them from sharing cached tokens.