503 matches found
CVE-2026-11101-HTTP-Cache-Poisoning-via-Unkeyed-Query-Parameter
CVE-2026-11101 – HTTP Cache Poisoning via Unkeyed Query Parameter Overview A web cache uses only the URL path as the cache key, ignoring query parameters. An attacker can append a malicious payload to an unkeyed parameter e.g., utmcampaign and poison the cache. Subsequent visitors receive the...
CVE-2025-53694
CVE-2025-53694: Information Disclosure in ItemService API with a restricted anonymous user, leading to exposure of cache keys using a brute-force approach The ItemService API, accessible at /sitecore/shell/api/sitecore/ItemService/GetChildren, allows unauthenticated users to query the Sitecore...
DHI-BYKH-ZCOR-W7ZB-GPQD Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.4.5, Next.js App Router…
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.4.5, Next.js App Router applications that pass binary arguments, such as Uint8Array or Blob values, to functions using the 'use cache' directive can generate identical cache keys for distinct arguments...
EUVD-2026-126594
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments...
EUVD-2026-128816
Grav from 2.0.0 before 2.2.18 contains an access control bypass vulnerability that allows anonymous visitors to read protected pages because admin and site scopes share a page cache key. Routine editor activity through the API plugin rebuilds the page index without frontmatter.yaml access rules,...
CVE-2026-35030-PoC
CVE-2026-35030 — LiteLLM Authentication Bypass via OIDC Userinfo Cache Key Collision LiteLLM OIDC userinfo cache uses token:20 as the cache key. Two different JWTs signed with the same algorithm produce identical first 20 characters , allowing an unauthenticated attacker to inherit another user's...
CVE-2026-119349
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.4.5, Next.js App Router applications that pass binary arguments, such as Uint8Array or Blob values, to functions using the 'use cache' directive can generate identical cache keys for distinct arguments...
CVE-2011-10042 HTTP::Session versions before 0.43 for Perl allow memcached command injection via unfiltered session ids in HTTP::Session::Store::Memcached
HTTP::Session versions before 0.43 for Perl allow memcached command injection via unfiltered session ids in HTTP::Session::Store::Memcached. The session id from the client's cookie reaches memcached unchanged as the cache key. A CR and LF in the session id end the cache command early, and the...
DHI-R35C-BOS5-ADE6-RV27 Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return…
Next.js versions from 16.3.0 to 16.3.7 warm use cache handlers using next/root-params and can leak their return value to pages with different root params. With Cache Components enabled cacheComponents: true, a 'use cache' function that calls another 'use cache' function that reads a root param ca...
CVE-2026-113593
A flaw was found in Django. This vulnerability leads to information disclosure due to improper cache key generation when handling HTTP headers. The caching mechanism treats web requests that omit a specified header identically to requests that supply the header with an empty value. As a result, a...
EUVD-2026-122965
The graphql-proxy-cache-advanced plugin in Kong Gateway Enterprise omits the caller's identity from the cache key, allowing a response cached for one caller to be served to another...
EUVD-2026-122960
The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway omit the request hostname from the cache key which may allow a response cached for a hostname to be served for another...
EUVD-2026-123056
The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway do not escape separator characters when building the cache key, allowing a remote attacker to cause a response cached for one request to be served for a different request on the same Route...
Node.js < 22.23.5, < 24.22.3, < 26.13.1 - Improper Certificate Validation via an https.Agent Session Cache Key Collision Between Omitted and Empty ca leading to Cross-Policy Session Reuse
Improper Certificate Validation via an https.Agent Session Cache Key Collision Between Omitted and Empty ca leading to Cross-Policy Session Reuse vulnerability discovered by ? in WordPress npm Node.js versions 26.13.1...
CVE-2026-92545
The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway omit the request hostname from the cache key which may allow a response cached for a hostname to be served for another...
CVE-2026-92558
The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway do not escape separator characters when building the cache key, allowing a remote attacker to cause a response cached for one request to be served for a different request on the same Route...
CVE-2026-92558
The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway are vulnerable to an improper encoding or escaping issue (CWE-116 ). The root cause is the failure to escape separator characters when constructing the cache key . This flaw allows a remote attacker to...
CVE-2026-92558
The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway do not escape separator characters when building the cache key, allowing a remote attacker to cause a response cached for one request to be served for a different request on the same Route...
CVE-2026-92442
The graphql-proxy-cache-advanced plugin in Kong Gateway Enterprise omits the caller's identity from the cache key, allowing a response cached for one caller to be served to another...
CVE-2026-92442
The graphql-proxy-cache-advanced plugin in Kong Gateway Enterprise is vulnerable to a cache poisoning issue because it omits the caller's identity from the cache key. This flaw allows a response cached for one user to be incorrectly served to another. No specific exploit details or remediation ve...