Skip to content
Fencer Vulns
medium 5.9

CVE-2026-48090 json

Envoy HTTP: OAuth2 filter late async token completion after stream teardown (UAF / crash risk)

published 2026-06-26 4 mo ago modified 2026-10-25 14 d ago also BIT-envoy-2026-48090 , EUVD-2026-39830 , GHSA-3cj2-c63f-q26f

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

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.

Patch / fix

  • bitnami envoy 1.37.5, 1.38.3
  • envoyproxy envoy 1.37.5, 1.38.3
  • istioctl openSUSE Tumbleweed 1.30.2-1.1

opensuse advisories openSUSE-SU-2026:11141-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-48090 updated cvss 5.9

envoy: Envoy HTTP: OAuth2 filter late async token completion after stream teardown (UAF / crash risk)

  • Red Hat OpenShift Service Mesh 2 openshift-service-mesh/proxyv2-rhel9 Red Hat OpenShift Service Mesh 3 openshift-service-mesh/istio-proxyv2-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-3cj2-c63f-q26f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami envoy
>=1.37.0, <1.37.5
>=1.38.0, <1.38.3
1.37.5
1.38.3

Affected products

  • envoyproxy envoy

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.