GHSA-2m8c-2374-465f: Duplicate Advisory Cache Poisoning Vulnerability
HIGHGHSA-2m8c-2374-465f is a HIGH cache poisoning vulnerability (General Security Weakness) affecting Duplicate Advisory libraries in the crates.io ecosystem. The issue involves cache poisoning via insecure-by-default cache key. Remediation is available by upgrading affected packages to version 0.8.0.
GHSA-2m8c-2374-465f at a Glance
How to Fix GHSA-2m8c-2374-465f
To remediate this vulnerability, upgrade all affected Duplicate Advisory dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade pingora-cache to 0.8.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for pingora-cache
How to Check if You Are Affected
To determine whether your application is affected by GHSA-2m8c-2374-465f, inspect your project dependencies for Duplicate Advisory:
inspect dependencies for pingora-cache
Analyze the terminal output to locate any version of Duplicate Advisory in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under General Security Weakness. In Duplicate Advisory, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-2m8c-2374-465f Affected Duplicate Advisory Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
pingora-cache
|
crates.io |
< 0.8.0
|
0.8.0
|
References
Frequently Asked Questions
What is GHSA-2m8c-2374-465f?
Which Duplicate Advisory versions are affected?
What version fixes GHSA-2m8c-2374-465f?
Is pingora-cache affected?
What CWE is associated with GHSA-2m8c-2374-465f?
How can I check crates.io dependencies for GHSA-2m8c-2374-465f?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2m8c-2374-465f",
"modified" : "2026-03-05T20:57:23Z",
"published" : "2026-03-05T00:31:11Z",
"withdrawn" : "2026-03-05T20:57:23Z",
"aliases" : [ ],
"summary" : "Duplicate Advisory: Cache poisoning via insecure-by-default cache key",
"details" : "### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-f93w-pcj3-rggc. This link is maintained to preserve external references.\n\n### Original Description\nA cache poisoning vulnerability has been found in the Pingora HTTP proxy framework’s default cache key construction. The issue occurs because the default HTTP cache key implementation generates cache keys using only the URI path, excluding critical factors such as the host header (authority). Operators relying on the default are vulnerable to cache poisoning, and cross-origin responses may be improperly served to users.\n\n\nImpact\n\nThis vulnerability affects users of Pingora's alpha proxy caching feature who relied on the default CacheKey implementation. An attacker could exploit this for:\n\n * Cross-tenant data leakage: In multi-tenant deployments, poison the cache so that users from one tenant receive cached responses from another tenant\n\n\n * Cache poisoning attacks: Serve malicious content to legitimate users by poisoning shared cache entries\n\n\n\n\nCloudflare's CDN infrastructure was not affected by this vulnerability, as Cloudflare's default cache key implementation uses multiple factors to prevent cache key poisoning and never made use of the previously provided default.\n\n\nMitigation:\n\nWe strongly recommend Pingora users to upgrade to Pingora v0.8.0 or higher, which removes the insecure default cache key implementation. Users must now explicitly implement their own callback that includes appropriate factors such as Host header, origin server HTTP scheme, and other attributes their cache should vary on.\n\n\nPingora users on previous versions may also remove any of their default CacheKey usage and implement their own that should at minimum include the host header / authority and upstream peer’s HTTP scheme.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "crates.io",
"name" : "pingora-cache"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.8.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-2836"
}, {
"type" : "WEB",
"url" : "https://github.com/cloudflare/pingora"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2026-0035.html"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-05T20:57:23Z",
"nvd_published_at" : "2026-03-05T00:15:58Z"
}
}