Envoy HTTP: OAuth2 filter late async token completion after stream teardown (UAF / crash risk)
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-48090
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 10:24 UTC · Revision 1
Source evidence
Envoy HTTP: OAuth2 filter late async token completion after stream teardown (UAF / crash risk)
core-osv · Original sourcePublished 26 Jun 2026, 18:03 UTC
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.
osv:CVE-2026-48090
Complete source record
{
"id": "1e175030df0114e16c3ebccc568af4cfd8cbc2cc9e7bb33349fee33f60be3b67",
"url": "https://osv.dev/vulnerability/CVE-2026-48090",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Envoy HTTP: OAuth2 filter late async token completion after stream teardown (UAF / crash risk)",
"summary": "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.",
"evidence": "osv:CVE-2026-48090",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-48090",
"aliases": [
"BIT-envoy-2026-48090",
"CVE-2026-48090",
"GHSA-3cj2-c63f-q26f"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/envoyproxy/envoy",
"type": "GIT",
"events": [
{
"introduced": "6d9bb7d9a85d616b220d1f8fe67b61f82bbdb8d3"
},
{
"fixed": "f97695a50e11f5ff6719e129a466bf9204b64a7f"
},
{
"introduced": "f1dd21b16c244bda00edfb5ffce577e12d0d2ec2"
},
{
"fixed": "0ebfcfe5b0484b89ca85b761da9e05ce75dbda8d"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.37.0"
},
{
"fixed": "1.37.5"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.38.0"
},
{
"fixed": "1.38.3"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v1.38.2",
"v1.37.4",
"v1.38.1",
"v1.37.3",
"v1.38.0",
"v1.37.2",
"v1.37.1",
"v1.37.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-48090.json"
}
}
],
"modified": "2026-10-28T02:30:27.840659396Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48090.json",
"https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f",
"https://nvd.nist.gov/vuln/detail/CVE-2026-48090"
],
"provider_metadata": {
"cwe_ids": [
"CWE-416"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48090.json"
}
},
"related_cves": [
{
"value": "CVE-2026-48090",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 494481,
"published_at": "2026-06-26T18:03:05.257+00:00"
}