CVE-2026-50572: envoyproxy envoy · Use After Free
Affects envoyproxy envoySource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium · fixed in 1.39.1 : update envoyproxy envoy when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.39.1, 1.38.4, 1.37.6 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade envoy and envoyproxy/envoy to 1.39.1, 1.38.4, 1.37.6 or 1.36.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
GitHubenvoyproxy/envoypkg:github/envoyproxy/envoyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Envoy to versions 1.36.10, 1.37.6, 1.38.4, or 1.39.1 or later where this issue is fixed. No other mitigation or temporary workaround is indicated by the advisory.
Description
CVE-2026-50572 is a use-after-free vulnerability in the Envoy proxy's HTTP external-authorization client. It occurs when a stale request callback is retained after a request rejection, leading to a process crash when the callback is invoked after its owner is destroyed. This issue affects specific versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 and is fixed in these versions.
References
- github.com/envoyproxy/envoy/security/advisories/GHSA-q8wp-gf7q-m8cv (opens in a new tab)
- github.com/envoyproxy/envoy/commit/8dacef38337aeffd62866b5c5910104b63b33db8 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/a49085623654e27e9ad6298928557644b849d7ce (opens in a new tab)
- github.com/envoyproxy/envoy/commit/c1b29534a294cb0999e99e1fe0de000310165f03 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/c524571ffad517ba650d9563f85afa89194e2cfb (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.36.10 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.37.6 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.38.4 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.39.1 (opens in a new tab)