cve.bz

CVE-2026-50572 envoyproxy envoy: Use After Free

5.9 mediumEPSS 0.7%Fix available

Medium (5.9) in envoyproxy envoy. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's HTTP external-authorization client can retain a stale request callback after a request is rejected. When RawHttpClientImpl::onSuccess later processes the authorization response, it can invoke callbacks_ after the callback owner has been destroyed, causing a use-after-free and process crash under production traffic. The relevant scope boundary is that the vulnerable path uses the HTTP ext_authz client; the advisory does not establish the same trigger for unrelated filters. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-50572 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50572?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50572?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50572 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-50572

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-50572](https://cve.bz/cve/badge/CVE-2026-50572.svg)](https://cve.bz/cve/CVE-2026-50572)

HTML:

<a href="https://cve.bz/cve/CVE-2026-50572"><img src="https://cve.bz/cve/badge/CVE-2026-50572.svg" alt="CVE-2026-50572"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
envoyproxy:envoybefore 1.36.10
envoyproxy:envoyfrom 1.37.0 before 1.37.6
envoyproxy:envoyfrom 1.38.0 before 1.38.4
envoyproxy:envoyfrom 1.39.0 before 1.39.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweedistioctl1.30.4-1.1openSUSE-SU-2026:11630-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is evaluated as having a Moderate impact for Red Hat products because triggering the crash requires non-default configurations and specific timing conditions, limiting the impact to denial of service without compromising system confidentiality or integrity. In typical OpenShift Service Mesh deployments, external authorization using an HTTP-based service is an optional extension rather than an enabled-by-default capability. When configured, an untrusted client must induce a race condition during authorization failure handling, terminating the proxy process but not allowing remote code execution or data leakage.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat OpenShift Service Mesh 3.0openshift-service-mesh/istio-proxyv2-rhel9:1788296328Fixed 2026-09-08RHSA-2026:65106
Red Hat OpenShift Service Mesh 3.1openshift-service-mesh/istio-proxyv2-rhel9:1788294715Fixed 2026-09-08RHSA-2026:65112
Red Hat OpenShift Service Mesh 3.2openshift-service-mesh/istio-proxyv2-rhel9:1788329366Fixed 2026-09-08RHSA-2026:65113
Red Hat OpenShift Service Mesh 3.3openshift-service-mesh/istio-proxyv2-rhel9:1788327866Fixed 2026-09-08RHSA-2026:65115
Red Hat OpenShift Service Mesh 3.4openshift-service-mesh/istio-proxyv2-rhel9:1788333924Fixed 2026-09-08RHSA-2026:65121

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-50572.

References

Check your stackJSON