cve.bz

CVE-2026-73513 envoyproxy envoy: Use After Free

7.5 highExploit referenceEPSS 0.5%Fix available

High (7.5) in envoyproxy envoy. EPSS 0.5% 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 optional oghttp2 upstream HTTP/2 codec accepts a response trailer HEADERS frame without END_STREAM. Envoy completes and deferred-deletes the ActiveRequest while oghttp2 keeps the stream open, leaving ClientStreamImpl with a dangling response_decoder_ reference. A later frame on the stream can dispatch through the freed object and crash the process. The relevant scope boundary is that the default nghttp2 codec rejects the malformed trailers, and the trigger is upstream-only with oghttp2 enabled. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-416 Use After Free
OWASP Top 10
A05:2025 Injection
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-73513 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73513?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73513?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-73513 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-73513

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-73513](https://cve.bz/cve/badge/CVE-2026-73513.svg)](https://cve.bz/cve/CVE-2026-73513)

HTML:

<a href="https://cve.bz/cve/CVE-2026-73513"><img src="https://cve.bz/cve/badge/CVE-2026-73513.svg" alt="CVE-2026-73513"></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 Important.

Red Hat's statement

This vulnerability is rated as an Important severity issue for Red Hat products because an untrusted upstream service can remotely trigger memory corruption, crashing the Envoy proxy process and causing a denial of service. The defect only affects instances where Envoy is explicitly configured to use the optional oghttp2 upstream HTTP/2 implementation instead of the default nghttp2 codec. In OpenShift Service Mesh environments, risk is isolated to deployments that route requests to untrusted backend destinations with this optional parser enabled.

Red Hat's mitigation

Ensure upstream HTTP/2 clusters rely on the default nghttp2 codec rather than enabling the optional oghttp2 codec. Where possible, restrict proxy routing configurations to communicate exclusively with trusted internal backend services.

Modifying upstream cluster configurations or rolling out configuration changes requires restarting or reloading affected proxy pods or services, which can cause brief connection interruptions.

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-73513.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON