CVE-2026-2835 HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing

Critical 9.3 Published Updated

Attackers can smuggle HTTP requests to bypass security controls and poison caches in Pingora proxy deployments.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-2835?

CVE-2026-2835 is a critical vulnerability in https://github.com/cloudflare/pingora, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

An HTTP Request Smuggling vulnerability (CWE-444) has been found in Pingora's parsing of HTTP/1.0 and Transfer-Encoding requests. The issue occurs due to improperly allowing HTTP/1.0 request bodies to be close-delimited and incorrect handling of multiple Transfer-Encoding values, allowing attackers to send HTTP/1.0 requests in a way that would desync Pingora’s request framing from backend servers’.

Impact

This vulnerability primarily affects standalone Pingora deployments in front of certain backends that accept HTTP/1.0 requests. An attacker could craft a malicious payload following this request that Pingora forwards to the backend in order to:

* Bypass proxy-level ACL controls and WAF logic

* Poison caches and upstream connections, causing subsequent requests from legitimate users to receive responses intended for smuggled requests

* Perform cross-user attacks by hijacking sessions or smuggling requests that appear to originate from the trusted proxy IP

Cloudflare's CDN infrastructure was not affected by this vulnerability, as its ingress proxy layers forwarded HTTP/1.1 requests only, rejected ambiguous framing such as invalid Content-Length values, and forwarded a single Transfer-Encoding: chunked header for chunked requests.

Mitigation:

Pingora users should upgrade to Pingora v0.8.0 or higher that fixes this issue by correctly parsing message length headers per RFC 9112 and strictly adhering to more RFC guidelines, including that HTTP request bodies are never close-delimited.

As a workaround, users can reject certain requests with an error in the request filter logic in order to stop processing bytes on the connection and disable downstream connection reuse. The user should reject any non-HTTP/1.1 request, or a request that has invalid Content-Length, multiple Transfer-Encoding headers, or Transfer-Encoding header that is not an exact “chunked” string match.

Weakness: CWE-444

Which versions are affected by CVE-2026-2835?

3 open source packages ship an affected version, including pingora-core. It affects 1 product.

PackageAffectedFixed in
pingora-core crates.ioAll versions0.8.0
pingora-core crates.ioAll versions0.8.0
pingora-core crates.ioFrom 0.0.0-00.8.0

Products include Cloudflare Pingora.

How do I fix CVE-2026-2835?

Upgrade pingora-core to 0.8.0 or later.

Is CVE-2026-2835 being exploited?

There is no known exploitation of CVE-2026-2835 in the wild and no public exploit code.

Sources

Also known as GHSA-hj7x-879w-vrp7, RUSTSEC-2026-0034.

Is CVE-2026-2835 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free