Advisory

RUSTSEC-2026-0035

Also known as: CVE-2026-2836, GHSA-f93w-pcj3-rggc

Summary

Cache poisoning via insecure-by-default cache key

Details

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.

This flaw was corrected in commit 257b59ada28ed6cac039f67d0b71f414efa0ab6e by removing the insecure default cache key implementation. Users must now explicitly implement their own callback that includes appropriate factors such as Host header and origin server HTTP scheme. We strongly recommend that users upgrade to Pingora >= 0.8.0.

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.

Severity

Not rated by the source.

Dates

Published
2026-03-04 12:00 UTC
Modified
2026-03-09 21:00 UTC

Affected packages and fixes

pingora-cache

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.8.0 (semver)

Fixed versions

0.8.0

Fix

  • Fixed version 0.8.0
    cargo update -p pingora-cache --precise 0.8.0

Fix 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

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences