CVE-2026-48743: Envoy: HTTP/3 to HTTP/1 request smuggling via headers-only request with nonzero Content-Length

Severity: high (CVSS 7.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-06-26 · updated 2026-10-25
Weakness: CWE-444

Description

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, Envoy can translate a downstream HTTP/3 request that is complete at the transport layer (HEADERS with FIN / headers-only close) but still carries a nonzero Content-Length into a complete upstream HTTP/1 request with unresolved body debt. In an HTTP/1 upstream deployment where the origin replies before reading the declared body and keeps the connection reusable, the beginning of the next Envoy-generated upstream request can be consumed as the first request's body. The remaining bytes are then parsed by the origin as a new HTTP/1 request. This was reproduced as a route-bypass/desync: direct /pwn was denied by Envoy, but the second downstream H3 stream received the response for backend-parsed GET /pwn HTTP/1.1. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1.

Affected products

envoyproxy envoy: from 1.35.0 before 1.35.13; from 1.36.0 before 1.36.9; from 1.37.0 before 1.37.5; from 1.38.0 before 1.38.3 — fixed in 1.35.13, 1.36.9, 1.37.5, 1.38.3

How to fix

Upgrade to a fixed version: envoyproxy envoy 1.35.13, 1.36.9, 1.37.5, 1.38.3. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-48743 or the next vulnerability affects your stack