CVE-2026-47207: envoyproxy envoy · Use After Free
Affects envoyproxy envoySource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 1.38.3 : update envoyproxy envoy when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.38.3, 1.37.5, 1.36.9 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Jun 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 7 Nov 2026.
What to do
Upgrade envoy and envoyproxy/envoy to 1.38.3, 1.37.5, 1.36.9 or 1.35.13.
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
Fixed versions are 1.35.13, 1.36.9, 1.37.5, and 1.38.3. Users should upgrade to one of these versions to remediate the vulnerability. Patch status is not explicitly confirmed in the vendor advisory, but the description states these versions contain the fix. No other mitigation or workaround is provided.
Description
Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.34.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, Envoy crashes if an ext_proc server sends a single gRPC message containing multiple, specially crafted ProcessingResponse messages. This can occur when the first response in the batch causes the gRPC stream object to be destroyed, leading to a use-after-free error when Envoy attempts to process subsequent responses in the same gRPC message. This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.