envoyproxy · Envoy · published 2026-09-21
CVE-2026-73551Envoy: Path normalization does not handle dot and dotdot segments with parameters
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-73551 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 45% of all CVEs. This Envoy vulnerability: CVSS 5.3 (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.5% (46th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | 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 URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. 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.