All vulnerabilities

Servers and applications

CVE-2026-47205

ext_authz Use-After-Free during Stream Teardown with Per-Route Overrides

Severity
Medium 5.9
Published
23 Jun 2026
Last changed
25 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
1.36.9, 1.37.5, 1.38.3
Exploit chance
0.4% in the next 30 daysHigher than 33% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Use after free (CWE-416)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Take it down
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Also known as
GHSA-mvh9-767w-x47j
Sources
NVD, Project advisories (GitHub)

Description

Vulnerability Type: Use-After-Free (UAF) Component: ext_authz filter Severity: HIGH (Data-plane crash/DoS)

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() ->…

From envoyproxy/envoy's security advisory. Shortened; the full text is there.

Workarounds

The upstream patch resolves the vulnerability by permanently preserving the core default client's memory lifecycle inside the filter context independently, insulating resource teardown routines from localized route evaluations.

A dedicated per_route_client_ unique pointer now safely binds the lifecycle of transient dynamic clients, while an active_client_ tracking pointer reliably dispatches fundamental cancel() commands during rapid stream destruction:

Workarounds as given by envoyproxy/envoy's security advisory.

Affected software

SoftwareAffected versions
EnvoyServers and applications · cpe:a:envoyproxy:envoy
  • From 1.36.0 before 1.36.9
  • From 1.37.0 before 1.37.5
  • From 1.38.0 before 1.38.3
EnvoyServers and applications · github:envoyproxy/envoy
  • From 1.36 before 1.36.9

About Envoy

service proxy

From Wikidata, CC0 1.0.
Docker Hub pulls
5,809,928,938Docker Hub, 15 Nov 2026
GitHub stars
29,237GitHub, 15 Nov 2026
Forks
5,728GitHub, 15 Nov 2026
Latest release
v1.40.2GitHub, 15 Nov 2026
Released
27 Oct 2026GitHub
Developer
Alyssa WilkWikidata
License
Apache Software License 2.0Wikidata
Written in
C++Wikidata
First released
8 Aug 2016Wikidata
First published on GitHub
8 Aug 2016GitHub

Release lines

ReleaseLatestSecurity fixes
1.401.40.2Until 13 Oct 2027
1.391.39.6Until 14 Jul 2027
1.381.38.9Until 23 Apr 2027
1.371.37.11Until 13 Jan 2027
1.361.36.13Ended 14 Oct 2026
1.351.35.13Ended 23 Jul 2026

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-47205
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-47205
  • GitHub Advisory Database https://github.com/advisories/GHSA-mvh9-767w-x47j
  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-mvh9-767w-x47j