Envoy: Path normalization does not handle dot and dotdot segments with parameters
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| envoyproxy | envoy | before 1.36.10; 1.37.0 to before 1.37.6; 1.38.0 to before 1.38.4; 1.39.0 to before 1.39.1 | 1.36.10, 1.37.6, 1.38.4, 1.39.1 | Patch available | CNA |
- envoy Vendorenvoyproxy Affected before 1.36.10; 1.37.0 to before 1.37.6; 1.38.0 to before 1.38.4; 1.39.0 to before 1.39.1 Fixed in 1.36.10, 1.37.6, 1.38.4, 1.39.1 Patch available CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* | before 1.36.10; 1.37.0 to before 1.37.6; 1.38.0 to before 1.38.4; 1.39.0 to before 1.39.1 | Vulnerable | envoyproxy |
- cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* Versions before 1.36.10; 1.37.0 to before 1.37.6; 1.38.0 to before 1.38.4; 1.39.0 to before 1.39.1 Vulnerable ·envoyproxy
Remediation
- Fix · CNA envoy (envoyproxy) Fixed in 1.36.10, 1.37.6, 1.38.4, 1.39.1
Red Hat 5 advisories
- RHSA-2026:65121 Released 2026-09-08 · Red Hat rating ImportantRed Hat OpenShift Service Mesh 3.4.2
- Red Hat OpenShift Service Mesh 3.4 registry.redhat.io/openshift-service-mesh/istio-cni-rhel9, registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9, registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9 +1
- RHSA-2026:65115 Released 2026-09-08 · Red Hat rating ImportantRed Hat OpenShift Service Mesh 3.3.7
- Red Hat OpenShift Service Mesh 3.3 registry.redhat.io/openshift-service-mesh/istio-cni-rhel9, registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9, registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9 +1
- RHSA-2026:65113 Released 2026-09-08 · Red Hat rating ImportantRed Hat OpenShift Service Mesh 3.2.9
- Red Hat OpenShift Service Mesh 3.2 registry.redhat.io/openshift-service-mesh/istio-cni-rhel9, registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9, registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9 +1
Show 2 more Red Hat advisories
- RHSA-2026:65112 Released 2026-09-08 · Red Hat rating ImportantRed Hat OpenShift Service Mesh 3.1.12
- Red Hat OpenShift Service Mesh 3.1 registry.redhat.io/openshift-service-mesh/istio-cni-rhel9, registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9, registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9 +1
- RHSA-2026:65106 Released 2026-09-08 · Red Hat rating ImportantRed Hat OpenShift Service Mesh 3.0.15
- Red Hat OpenShift Service Mesh 3.0 registry.redhat.io/openshift-service-mesh/istio-cni-rhel9, registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9, registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9 +1
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat OpenShift Service Mesh 3.0 | Fixed | RHSA-2026:65106 |
| Red Hat OpenShift Service Mesh 3.1 | Fixed | RHSA-2026:65112 |
| Red Hat OpenShift Service Mesh 3.2 | Fixed | RHSA-2026:65113 |
| Red Hat OpenShift Service Mesh 3.3 | Fixed | RHSA-2026:65115 |
| Red Hat OpenShift Service Mesh 3.4 | Fixed | RHSA-2026:65121 |
Not affected: 5 products
- Red Hat OpenShift Service Mesh 3.0
- Red Hat OpenShift Service Mesh 3.1
- Red Hat OpenShift Service Mesh 3.2
- Red Hat OpenShift Service Mesh 3.3
- Red Hat OpenShift Service Mesh 3.4
Timeline
- 2026-10-02 Threatist record created from CVE-2026-73551
References
Patch 4
- https://github.com/envoyproxy/envoy/commit/28b6d60a6d96edeece121cac5be701eb46cc7f24
- https://github.com/envoyproxy/envoy/commit/d40a68b0a30a003c4e0a9fd3af637f828b52c37b
- https://github.com/envoyproxy/envoy/commit/e9d6c329f9a3ff19432bf39b60c601df7e3eda33
- https://github.com/envoyproxy/envoy/commit/f74d1107c4f5c9679b66f7a03a6c5b75ddde1989
More envoyproxy Envoy vulnerabilities
- TI-2026-79288 Out-of-bounds write in Google Brotli decoder KEVCVSS 4.0CRITICAL 9.2
- TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
- TI-2024-20001 HTTP/2: CPU exhaustion due to CONTINUATION frame flood CVSS 3.1HIGH 7.5
- TI-2024-18524 HTTP/2: memory exhaustion due to CONTINUATION frame flood CVSS 3.1HIGH 7.5
- TI-2023-12215 Envoy client may fake the header `x-envoy-original-path` CVSS 3.1CRITICAL 9.1
- TI-2023-18002 Envoy vulnerable to OAuth2 credentials exploit with permanent validity CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-73551 · CVE Program
- CVE-2026-73551 · NVD
- FIRST EPSS
- CVE-2026-73551 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences