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

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

CVE-2026-100701

A flaw was found in nodemailer. In multi-tenant environments, a remote attacker can exploit a cache confusion vulnerability by priming the shared Domain Name System DNS cache with a custom Transport Layer Security TLS server name. Because cached entries overwrite subsequent connection...

CVE-2026-100701 Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion

Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports secure: true resolve the same non-IP host with different tls.servername values, t...

CVE-2026-100701 Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion

Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports secure: true resolve the same non-IP host with different tls.servername values, t...

CVE-2026-100701 Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion

Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports secure: true resolve the same non-IP host with different tls.servername values, t...

Cache confusion in gitlab-plugin

gitlab-plugin allows jobs to override the globally configured GitLab API token credentials with an alternative one, and caches the GitLab API client it builds for those credentials. gitlab-plugin 1.2149.vcfc32c82bf7f and earlier derives the cache key from the credentials ID alone, omitting the...

CVE-2026-82755 ash_authentication_oauth2_server serves tenant-specific OAuth metadata as publicly cacheable without Vary, enabling cross-tenant confusion

Use of Cache Containing Sensitive Information vulnerability in ash-project ashauthenticationoauth2server allows a shared HTTP cache to serve one tenant's OAuth discovery metadata to another tenant's clients. The RFC 8414 and RFC 9728 metadata endpoints in...

GHSA-78X9-FHHX-V2G6 CKAN MCP Server: Cache-key canonicalization collision enables cache confusion / poisoning

Summary The response cache derives its key from an ambiguous string serialization of the request parameters. canonicalizeParams joins sorted $key=$value pairs with & and does not escape &, =, or the | field separators used in buildCacheKey. Two different logical parameter sets can therefore...

CVE-2026-73846 CKAN MCP Server: Cache-key canonicalization collision enables cache confusion / poisoning

CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, canonicalizeParams in src/utils/cache.ts serializes request parameters with unescaped ampersand, equals-sign, and vertical-bar delimiters, allowing different logical parameter sets used by buildCacheKey to collide an...

CVE-2026-73846 CKAN MCP Server: Cache-key canonicalization collision enables cache confusion / poisoning

CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, canonicalizeParams in src/utils/cache.ts serializes request parameters with unescaped ampersand, equals-sign, and vertical-bar delimiters, allowing different logical parameter sets used by buildCacheKey to collide an...

CVE-2026-73846 CKAN MCP Server: Cache-key canonicalization collision enables cache confusion / poisoning

CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, canonicalizeParams in src/utils/cache.ts serializes request parameters with unescaped ampersand, equals-sign, and vertical-bar delimiters, allowing different logical parameter sets used by buildCacheKey to collide an...

Cache Confusion

Next.js is vulnerable to Cache Confusion. The vulnerability is due to improper caching of server-side fetch responses, where cached response bodies may be reused across requests with different request bodies, allowing confidential data from one request to be exposed to unauthorized users...

NPM: Next.js: Cache confusion of response bodies for requests with bodies

NPM: Next.js: Cache confusion of response bodies for requests with bodies vulnerability discovered by ? in WordPress Npm next versions = 13.0.0, 15.5.21...

GHSA-68G3-V927-F742 Next.js: Cache confusion of response bodies for requests with bodies

Impact A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to...

Next.js: Cache confusion of response bodies for requests with bodies

Impact A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to...

NPM: Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences

NPM: Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences vulnerability discovered by ? in WordPress Npm next versions = 13.0.0, 15.5.21...

PYSEC-2026-1245 check-jsonschema default caching for remote schemas allows for cache confusion

Impact The default cache strategy uses the basename of a remote schema as the name of the file in the cache, e.g. https://example.org/schema.json will be stored as schema.json. This naming allows for conflicts. If an attacker can get a user to run check-jsonschema against a malicious schema URL,...

check-jsonschema default caching for remote schemas allows for cache confusion

ImpactThe default cache strategy uses the basename of a remote schema as the name of the file in the cache, e.g. https://example.org/schema.json will be stored as schema.json. This naming allows for conflicts. If an attacker can get a user to run check-jsonschema against a malicious schema URL,...