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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f Exploit, Mitigation, Vendor Advisory
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f Exploit, Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.9 · envoyproxyNVD modified 2026-10-25 17:10
Affected (CPE criteria) 1
cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
References 2
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f Exploit, Mitigation, Vendor Advisory
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f Exploit, Mitigation, Vendor Advisory