Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. pingora-cache
  4. ›
  5. CVE-2026-2836

CVE-2026-2836: Pingora vulnerable to cache poisoning via insecure-by-default cache key

March 5, 2026

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.

References

  • github.com/advisories/GHSA-f93w-pcj3-rggc
  • github.com/cloudflare/pingora
  • github.com/cloudflare/pingora/security/advisories/GHSA-f93w-pcj3-rggc
  • nvd.nist.gov/vuln/detail/CVE-2026-2836
  • rustsec.org/advisories/RUSTSEC-2026-0035.html

Code Behaviors & Features

Detect and mitigate CVE-2026-2836 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.8.0

Fixed versions

  • 0.8.0

Solution

Upgrade to version 0.8.0 or above.

Impact 9.3 CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Learn more about CVSS

Weakness

  • CWE-639: Authorization Bypass Through User-Controlled Key

Source file

cargo/pingora-cache/CVE-2026-2836.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Fri, 06 Mar 2026 12:18:58 +0000.