envoyproxy · Envoy · published 2026-09-21
CVE-2026-73547Envoy ext_authz: request `:path` pseudoheader dereferenced w/o null check
Routine No exploitation evidence; EPSS 0.6%.
CVE-2026-73547 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 47% of all CVEs. This Envoy vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10.
Patch events
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.10Why: CVE-2026-73512: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.6% (47th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.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 exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- envoyproxy envoy
< 1.36.10(affected)>= 1.37.0, < 1.37.6(affected)>= 1.38.0, < 1.38.4(affected)>= 1.39.0, < 1.39.1(affected)
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 ext_authz filter assumes that a request contains a :path pseudoheader when applying query_parameters_to_set or query_parameters_to_remove from an authorization response. A path-less CONNECT request makes request_headers_->Path() return null, and Filter::onComplete dereferences that pointer while parsing the query string. An unauthenticated downstream client can crash the Envoy process when the filter and authorization response use query-parameter mutation. The relevant scope boundary is that the deployment must accept path-less CONNECT and configure ext_authz query-parameter mutation. 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.