envoyproxy · Envoy · published 2026-06-26

CVE-2026-47205Envoy: ext_authz Use-After-Free during Stream Teardown with Per-Route Overrides

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-47205 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 33% of all CVEs. This Envoy vulnerability: CVSS 5.9 (v3.1). Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13.

Patch events

  1. This monthSecurity release

    Web serverEnvoy

    Envoy security releases: 1.38.3, 1.37.5, 1.36.9, 1.35.13

    Upgrade to 1.38.31.37.51.36.91.35.13

    Why: CVE-2026-47220: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (34th pct)FIRST EPSS v2026.06.15
CVSS base score5.9 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.36.0 until 1.36.9, 1.37.5, and 1.38.3, a Use-After-Free (UAF) vulnerability leading to a sudden segmentation fault exists in Envoy's ext_authz HTTP filter when processing per-route authorization overrides concurrently with rapid downstream client disconnects. During standard request lifecycles, Envoy instantiates the ext_authz filter with a foundational authorization client object (client_). If a matched route dictates a dynamic per-route HTTP or gRPC authorization service override, the filter generates a localized client. In the vulnerable implementation, this transient client aggressively overwrote the default client_ unique pointer by executing client_ = std::move(per_route_client). When a client rapidly establishes and subsequently tears down a stream (such as rapidly refreshing a protected WebSocket endpoint), the downstream triggers the ConnectionManagerImpl::doDeferredStreamDestroy() -> ActiveStream::onResetStream() lifecycle. Envoy immediately sequences Filter::onDestroy() in an attempt to securely abort dispatched asynchronous authorization check transactions via client_->cancel(). By destructing the default client abruptly during initiateCall, a memory lifecycle misalignment occurs within the async client manager. The stream teardown fails to reliably track and cancel the dynamically bound asynchronous authorization tasks, orchestrating a sequence where a late asynchronous callback from the network evaluates against a heavily destroyed ActiveStream validation span, generating a UAF process crash. This vulnerability is fixed in 1.36.9, 1.37.5, and 1.38.3.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →