envoyproxy · Envoy · published 2026-06-26
CVE-2026-48090Envoy HTTP: OAuth2 filter late async token completion after stream teardown (UAF / crash risk)
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-48090 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 48% 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.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13.
Patch events
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.13Why: CVE-2026-47220: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.6% (49th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.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 exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- envoyproxy envoy
>= 1.38.0, < 1.38.3(affected)>= 1.37.0, < 1.37.5(affected)
Description (from the CVE record)#
Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.37.0 until 1.37.5 and 1.38.3, the HTTP OAuth2 filter (envoy.filters.http.oauth2) can leave an in-flight async token exchange attached to a downstream stream that has already been torn down. A late AsyncClient completion can still invoke OAuth2Filter methods that use StreamDecoderFilterCallbacks after that object’s lifetime has ended, causing undefined behavior, worker crashes (availability loss), and use-after-free / invalid-vptr failures under AddressSanitizer. This is a memory-safety / lifetime issue in the data plane, not a trivial config bug. Remote code execution is not claimed here; the primary demonstrated impact is DoS via crash and UB; any further impact would be deployment- and allocator-dependent. This vulnerability is fixed in 1.37.5 and 1.38.3.
Quoted from the CVE Program record.