envoyproxy · Envoy · published 2026-06-26
CVE-2026-48743Envoy: HTTP/3 to HTTP/1 request smuggling via headers-only request with nonzero Content-Length
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-48743 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 23% of all CVEs. This Envoy vulnerability: CVSS 7.5 (v3.1). Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13.
Patch events
Web serverEnvoy
Envoy security releases: 1.38.3, 1.37.5, 1.36.9, 1.35.13
Upgrade to
1.38.31.37.51.36.91.35.13Why: CVE-2026-47220: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (23th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- envoyproxy envoy
>= 1.38.0, < 1.38.1(affected)>= 1.37.0, < 1.37.3(affected)>= 1.36.0, < 1.36.7(affected)>= 1.35.0, < 1.35.11(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.