Envoy: use-after-free in QUIC on internal redirects
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's HttpDatagramHandler caches the current RequestDecoder when Capsule Protocol is enabled. Stream recreation, including an internal redirect, replaces the ActiveStream and updates EnvoyQuicServerStream but does not update the handler's cached pointer. A subsequent HTTP/3 datagram can call decodeData through the freed decoder, causing invalid virtual dispatch and a process crash. The relevant scope boundary is that hTTP/3 datagrams and Capsule Protocol must be enabled, and the request must enter a stream-recreation path such as an internal redirect. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-73512US | — | — | ||
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's HttpDatagramHandler caches the current… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/envoyproxy/envoy/commit/29dbaae4a9971011e2f1948acfaf383296e901eaFIX
- https://github.com/envoyproxy/envoy/commit/85495163fdc67364a5258bfe478c34a44f6428b4FIX
- https://github.com/envoyproxy/envoy/commit/c0e46dabc3ac286bbe608e9274776555911aadb9FIX
- https://github.com/envoyproxy/envoy/commit/f2417eec2ff49abe243d484ded916fbc2faca38dFIX
- https://github.com/envoyproxy/envoy/releases/tag/v1.36.10ARTICLE
- https://github.com/envoyproxy/envoy/releases/tag/v1.37.6ARTICLE
- https://github.com/envoyproxy/envoy/releases/tag/v1.38.4ARTICLE
- https://github.com/envoyproxy/envoy/releases/tag/v1.39.1ARTICLE
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan