CVE-2026-73551

Envoy: Path normalization does not handle dot and dotdot segments with parameters

State
Published
Severity
5.3 Medium
Published
Sep 21, 2026
Updated
Sep 28, 2026
Reserved
Aug 12, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.15.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NGitHub_M

Weaknesses

  • CWE-647 Use of Non-Canonical URL Paths for Authorization Decisions

Affected Products

ProductVersions
envoyenvoyproxy
  • < 1.36.10Affected
  • >= 1.37.0, < 1.37.6Affected
  • >= 1.38.0, < 1.38.4Affected
  • >= 1.39.0, < 1.39.1Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.