envoyproxy · Envoy · published 2026-06-26

CVE-2026-47220Envoy: Segmentation fault when using %REQUESTED_SERVER_NAME% in log format

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

CVE-2026-47220 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 52% of all CVEs. This Envoy vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13.

Patch events

  1. This monthSecurity release

    Web serverEnvoy

    Envoy security releases: 1.38.3, 1.37.5, 1.36.9, 1.35.13

    Upgrade to 1.38.31.37.51.36.91.35.13

    Why: CVE-2026-47220: 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% (53th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableYesCISA 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. From 1.37.0 until 1.37.5 and 1.38.3, when the %REQUESTED_SERVER_NAME(X:Y)% is used in log format and host related options is specified, like HOST_FIRST, SNI_FIRST, it's possible to crash Envoy when the specified host header is missing in the request headers. This vulnerability is fixed in 1.37.5 and 1.38.3.

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 →