envoyproxy · Envoy · published 2026-09-21

CVE-2026-48521Envoy: HTTP/3 connection pool selection null-derefs in ProdClusterManagerFactory::allocateConnPool when transport_socket_options is null

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-48521 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 55% of all CVEs. This Envoy vulnerability: CVSS 5.9 (v3.1). Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10.

Patch events

  1. This monthSecurity release

    Web serverEnvoy

    Envoy security releases: 1.39.1, 1.38.4, 1.37.6, 1.36.10

    Upgrade to 1.39.11.38.41.37.61.36.10

    Why: CVE-2026-73512: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.7% (55th pct)FIRST EPSS v2026.06.15
CVSS base score5.9 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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 ProdClusterManagerFactory::allocateConnPool dereferences transport_socket_options while selecting an HTTP/3 connection pool without first checking whether the pointer is null. LoadBalancerContext implementations used by synthetic, mirror, health-check, and async-client calls can return no transport-socket options. With auto_config and HTTP/3 enabled, routine traffic reaching one of those contexts can crash an Envoy worker. The relevant scope boundary is that the affected branch requires HTTP/3 in the protocol set and a context that supplies no transport-socket options. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →