envoyproxy · Envoy · published 2026-09-21
CVE-2026-73548Envoy: Cross-user response poisoning via a generic (non-WebSocket) HTTP upgrade on Envoy's shared backend pool
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-73548 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 41% of all CVEs. This Envoy vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10.
Patch events
Web serverEnvoy
Envoy security releases: 1.39.1, 1.38.4, 1.37.6, 1.36.10
Upgrade to
1.39.11.38.41.37.61.36.10Why: CVE-2026-73512: 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.5% (41th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- envoyproxy envoy
< 1.36.10(affected)>= 1.37.0, < 1.37.6(affected)>= 1.38.0, < 1.38.4(affected)>= 1.39.0, < 1.39.1(affected)
Description (from the CVE record)#
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy forwards data for a configured non-WebSocket HTTP upgrade before the upstream accepts the upgrade. An unauthenticated HTTP/2 client can place a complete HTTP/1.1 request in extended CONNECT data; Envoy downgrades the request, writes the data unframed to a keep-alive HTTP/1.1 upstream, and returns the socket to the shared pool while the smuggled response remains queued. A different downstream client can then receive the attacker's response. The relevant scope boundary is that webSocket upgrades, plain CONNECT, disabled backend keep-alive, per-downstream pools, and max_requests_per_connection set to 1 are not affected by the demonstrated path. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Quoted from the CVE Program record.