Skip to content
Fencer Vulns
medium 6.5

CVE-2026-47207 json

Envoy crashes if multiple unexpected ext_proc responses are packed into one gRPC message

published 2026-06-26 4 mo ago modified 2026-10-25 14 d ago also BIT-envoy-2026-47207 , EUVD-2026-39826 , GHSA-68cv-hq5f-g6xv

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami envoy 1.35.13, 1.36.9, 1.37.5, 1.38.3
  • envoyproxy envoy 1.35.13, 1.36.9, 1.37.5, 1.38.3
  • istioctl openSUSE Tumbleweed 1.30.2-1.1

opensuse advisories openSUSE-SU-2026:11141-1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-68cv-hq5f-g6xv referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami envoy
>=1.34.0, <1.35.13
>=1.36.0, <1.36.9
>=1.37.0, <1.37.5
>=1.38.0, <1.38.3
1.35.13
1.36.9
1.37.5
1.38.3

Affected products

  • envoyproxy envoy

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.