cve.bz

CVE-2026-47207 envoyproxy envoy: Use After Free

6.5 mediumExploit referenceEPSS 0.4%

Medium (6.5) in envoyproxy envoy. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-06-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-47207 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-47207?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-47207?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-47207 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-47207

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-47207](https://cve.bz/cve/badge/CVE-2026-47207.svg)](https://cve.bz/cve/CVE-2026-47207)

HTML:

<a href="https://cve.bz/cve/CVE-2026-47207"><img src="https://cve.bz/cve/badge/CVE-2026-47207.svg" alt="CVE-2026-47207"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
envoyproxy:envoyfrom 1.34.0 before 1.35.13
envoyproxy:envoyfrom 1.36.0 before 1.36.9
envoyproxy:envoyfrom 1.37.0 before 1.37.5
envoyproxy:envoyfrom 1.38.0 before 1.38.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweedistioctl1.30.2-1.1openSUSE-SU-2026:11141-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

References

Check your stackJSON