CVE-2026-85317

CVE-2026-85317 — camel-http: OAuth2 token cache confusion Runnable proof-of-concept reproducer for the Apache Camel vulnerability where camel-http's OAuth2 client token cache — a JVM-globalstatic map — keyed its entries on only uri, clientId, clientSecret, omitting the fields that actually shape...

CVE-2026-94386

CVE-2026-94386 — camel-oauth: cross-scope token reuse via an under-keyed JVM-global token cache Runnable proof-of-concept reproducer for the Apache Camel vulnerability where OAuthClientCredentialsTokenResolver kept the client-credentials tokens it obtained in a static cache shared by every resolv...

CVE-2026-85317

A flaw was found in the Apache Camel HTTP component. The OAuth2 authentication token cache incorrectly shares stored tokens across different endpoints because key authorization attributes, such as requested permissions and target service destinations, are omitted from the cache key. In...

CVE-2026-94386 Apache Camel: Camel-OAuth Cross-Scope Token Reuse via an Under-Keyed JVM-Global Client Credentials Token Cache

Use of Cache Containing Sensitive Information vulnerability in Apache Camel Oauth component. This issue affects Apache Camel: from 4.19.0 before 4.22.2. OAuthClientCredentialsTokenResolver obtains OAuth 2.0 bearer tokens through the client credentials grant on behalf of the components that...

PT-2026-123374

Use of Cache Containing Sensitive Information vulnerability in Apache Camel Oauth component. This issue affects Apache Camel: from 4.19.0 before 4.22.2. OAuthClientCredentialsTokenResolver obtains OAuth 2.0 bearer tokens through the client credentials grant on behalf of the components that...

Exploit for CVE-2026-85317

CVE-2026-85317 — camel-http: OAuth2 token cache confusion Run...

Apache Camel 4.22.0 OAuth2 Token Cache Confusion

Apache Camel camel-http versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1 contain an OAuth2 token-cache flaw that can reuse a token across endpoints differing by scope, resource indicator, or token endpoint. The supplied proof of concept demonstrates the behavior...

Use of Cache Containing Sensitive Information

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...

CVE-2026-85317

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 tok...

CVE-2026-85317

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 tok...

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

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 tok...

EUVD-2026-104205

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 tok...

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

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 tok...

CVE-2026-85317

The Apache Camel HTTP component is vulnerable to an OAuth2 Token Confusion issue due to an under-keyed JVM-global token cache. Specifically, the cache key omits the requested scope , resource indicator , and token endpoint , causing multiple distinct endpoints to share the same cache entry. This ...

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

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 tok...

PT-2026-117364

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 tok...

CVE-2026-85317: Use of Cache Containing Sensitive Information

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 tok...

EUVD-2026-97864

Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable...

CVE-2026-84321

Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, GenerateShortToken creates standalone short-token records without a long Token value, but DeleteUserTokens invalidates cached entries only when the long Token field is nonempty. A revoked short token can therefore remain i...

CVE-2026-107332

Insecure file permissions in the CodeCatalyst connection handler in AWS Toolkit for VS Code before 4.10.0 allowed local users to obtain CodeCatalyst bearer tokens via reading world-readable token cache files. To mitigate this issue, users should upgrade to version 4.10.0 or later...