CVE-2026-73512
highpriority · track · 0EPSS 0.009 · 59 %ileUSEPSS · scored 2026-10-28
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.9–7.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (8)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- BIT-envoy-2026-73512Envoy: use-after-free in QUIC on internal redirects2026-09-29vendor · osvUS
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.
also known as (1)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (9) nvd
External citations — patches, advisories, analysis.
- https://github.com/envoyproxy/envoy/commit/29dbaae4a9971011e2f1948acfaf383296e901eaPatch
- https://github.com/envoyproxy/envoy/commit/85495163fdc67364a5258bfe478c34a44f6428b4Patch
- https://github.com/envoyproxy/envoy/commit/c0e46dabc3ac286bbe608e9274776555911aadb9Patch
- https://github.com/envoyproxy/envoy/commit/f2417eec2ff49abe243d484ded916fbc2faca38dPatch
- https://github.com/envoyproxy/envoy/releases/tag/v1.36.10Release Notes
- https://github.com/envoyproxy/envoy/releases/tag/v1.37.6Release Notes
- https://github.com/envoyproxy/envoy/releases/tag/v1.38.4Release Notes
- https://github.com/envoyproxy/envoy/releases/tag/v1.39.1Release Notes
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan