Email me

Rust advisories / pingora-core

Vulnerability CriticalRUSTSEC-2026-0034 · pingora-core

RUSTSEC-2026-0034: HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing

Short answerA security vulnerability in the pingora-core crate: HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing. GitHub rates it Critical. Fixed in 0.8.0: update to a fixed version.

Cratepingora-core
TypeVulnerability
Affected versionsBefore 0.8.0.
Fixed in0.8.0
SeverityCritical (GitHub rating)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N
Published2026-03-04
Last changed2026-03-09
Also known asCVE-2026-2835, GHSA-hj7x-879w-vrp7

What to do

  1. See which version you have: cargo tree -i pingora-core (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p pingora-core. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example pingora-core = "0.8.0") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

Pingora versions prior to 0.8.0 improperly allowed HTTP/1.0 request bodies to be close-delimited and incorrectly handled multiple Transfer-Encoding values. This allows an attacker to desync Pingora's request framing from backend servers and smuggle requests to the backend.

This vulnerability primarily affects standalone Pingora deployments in front of certain backends that accept HTTP/1.0 requests. An attacker could exploit this to bypass proxy-level ACL controls and WAF logic, poison caches and upstream connections, or perform cross-user attacks by hijacking sessions.

This flaw was corrected in commits 7f7166d62fa916b9f11b2eb8f9e3c4999e8b9023, 40c3c1e9a43a86b38adeab8da7a2f6eba68b83ad, and 87e2e2fb37edf9be33e3b1d04726293ae6bf2052 by correctly parsing message length headers per RFC 9112. Users should upgrade to Pingora >= 0.8.0.

Note: Cloudflare customers and Cloudflare's CDN infrastructure were not affected by this vulnerability, as its ingress proxy layers rejected ambiguous framing such as invalid Content-Length values and internally forwarded non-ambiguous message length framing headers.

References

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for pingora-core

Full security history of pingora-core

Up next

Same cratepingora-core: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ