CVE-2026-48090: CWE-416: Use After Free in envoyproxy envoy
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.
AI Analysis
Technical Summary
Envoy proxy versions 1.37.0 through 1.37.4 and version 1.38.3 contain a use-after-free vulnerability (CWE-416) in the HTTP OAuth2 filter (envoy.filters.http.oauth2). An asynchronous token exchange can remain linked to a downstream stream after it has been torn down, causing late AsyncClient completions to invoke methods on freed objects. This results in undefined behavior, including worker crashes and invalid pointer dereferences, primarily causing denial of service. The vulnerability is a memory safety issue in the data plane and does not claim remote code execution. It is fixed in versions 1.37.5 and 1.38.3.
Potential Impact
The vulnerability can cause worker crashes and availability loss due to use-after-free conditions and undefined behavior in the Envoy data plane. There is no confirmed impact on confidentiality or integrity, and remote code execution is not claimed. The primary impact is denial of service through process crashes.
Mitigation Recommendations
This vulnerability is fixed in Envoy versions 1.37.5 and 1.38.3. Users should upgrade to these versions or later to remediate the issue. Patch status is not explicitly stated beyond these fixes; therefore, verify with the vendor advisory for the latest remediation guidance.
CVE-2026-48090: CWE-416: Use After Free in envoyproxy envoy
Description
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.
CVSS v3.1
Score 5.9medium
Affected software
pkg:github/envoyproxy/envoyRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Envoy proxy versions 1.37.0 through 1.37.4 and version 1.38.3 contain a use-after-free vulnerability (CWE-416) in the HTTP OAuth2 filter (envoy.filters.http.oauth2). An asynchronous token exchange can remain linked to a downstream stream after it has been torn down, causing late AsyncClient completions to invoke methods on freed objects. This results in undefined behavior, including worker crashes and invalid pointer dereferences, primarily causing denial of service. The vulnerability is a memory safety issue in the data plane and does not claim remote code execution. It is fixed in versions 1.37.5 and 1.38.3.
Potential Impact
The vulnerability can cause worker crashes and availability loss due to use-after-free conditions and undefined behavior in the Envoy data plane. There is no confirmed impact on confidentiality or integrity, and remote code execution is not claimed. The primary impact is denial of service through process crashes.
Mitigation Recommendations
This vulnerability is fixed in Envoy versions 1.37.5 and 1.38.3. Users should upgrade to these versions or later to remediate the issue. Patch status is not explicitly stated beyond these fixes; therefore, verify with the vendor advisory for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-20T18:40:45.833Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3eca5d72d29f1837deddee
Added to database: 06/26/2026, 18:52:13 UTC
Last enriched: 07/09/2026, 08:38:13 UTC
Last updated: 08/09/2026, 03:05:06 UTC
Views: 72
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.