CVE-2026-47220

Envoy: Segmentation fault when using %REQUESTED_SERVER_NAME% in log format

Published Jun 26, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Envoy is vulnerable to a null pointer dereference that triggers a segmentation fault when the log format includes the %REQUESTED_SERVER_NAME% macro together with host‑related options such as HOST_FIRST or SNI_FIRST and the incoming HTTP request lacks a host header. This crash leads to an abrupt termination of the Envoy process and an interruption of service for any clients attached to the affected proxy instance. The weakness is a classic CWE‑476 scenario, and the impact is a denial of service at the edge of a cloud‑native application stack.

Affected Systems

The vulnerability affects Envoy proxy versions 1.37.0 through 1.37.4 and 1.38.0 through 1.38.2. It has been fixed in 1.37.5 and 1.38.3, and later releases are not vulnerable. All installations using the default host‑resolution settings with %REQUESTED_SERVER_NAME% in the log format should verify their current Envoy version.

Risk and Exploitability

The CVSS score of 7.5 reflects a high severity of a crash‑induced denial of service. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, meaning no publicly known exploitation has been reported. The likely attack vector is a carefully crafted HTTP request sent to the Envoy service with a missing host header while host‑related options are active. An attacker who proxy can cause it to crash, potentially disrupting traffic for all downstream services.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Envoy to 1.37.5 or later (including 1.38.3 and later releases)
  • If upgrading is not immediately possible, remove the %REQUESTED_SERVER_NAME% placeholder from the log format or disable host‑related options such as HOST_FIRST and SNI_FIRST to prevent the crash scenario
  • Restart the Envoy process after configuration changes and monitor logs for any remaining segmentation fault events

Generated by OpenCVE AI on June 26, 2026 at 20:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Envoyproxy
Envoyproxy envoy
Vendors & Products Envoyproxy
Envoyproxy envoy
Type Values Removed Values Added
Description 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.
Title Envoy: Segmentation fault when using %REQUESTED_SERVER_NAME% in log format
Weaknesses CWE-476
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 12:49 AM
Reserved
May 18, 2026, 10:25 PM
Status
Modified
Published
Jun 26, 2026, 7:16 PM
Modified
Oct 25, 2026, 5:10 PM
Severity
Important
Public date
Jun 26, 2026, 6:02 PM