pingora-cache
Affected
- introduced
0, fixed0.8.0(semver)
Fixed versions
0.8.0
Fix
- Fixed version
0.8.0cargo update -p pingora-cache --precise 0.8.0
Advisory
Also known as: CVE-2026-2836, RUSTSEC-2026-0035
Pingora vulnerable to cache poisoning via insecure-by-default cache key
Impact
Pingora versions prior to 0.8.0 generated cache keys using only the URI path, excluding critical factors such as the host header. This allows an attacker to poison the cache and serve cross-origin responses to users.
This vulnerability affects users of Pingora's alpha proxy caching feature who relied on the default CacheKey implementation. An attacker could exploit this for cross-tenant data leakage in multi-tenant deployments, or serve malicious content to legitimate users by poisoning shared cache entries.
Note: Cloudflare customers and Cloudflare's CDN infrastructure were 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.
Patches
We strongly suggest users should upgrade to Pingora v.0.8.0 or higher, which removes the default CacheKey implementation.
Workarounds
Do not rely on the provided CacheKey default, and at minimum use the host / :authority and the upstream peer TLS scheme as part of building the CacheKey, as well as other factors that may apply to the deployment e.g. HTTP method.
References
See CVE-2026-2836 and the Cloudflare blog post for more details.
Credits
Disclosed responsibly by Rajat Raghav (@xclow3n) through the Cloudflare Bug Bounty Program.
High Basis: The source's own band: HIGH
0, fixed 0.8.0 (semver)0.8.0
0.8.0cargo update -p pingora-cache --precise 0.8.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0