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.
Published: 2026-09-21
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: Unauthorized File Access
Action: Assess Impact
AI Analysis

Impact

This vulnerability allows an attacker to exploit a path normalization bypass in the Envoy proxy, using dot and dot‑dot segments combined with request parameters to reference files or directories outside the intended scope. The issue enables unauthorized reading of protected resources, consistent with path traversal weaknesses (CWE‑22). While there is no detailed description, the CVE title indicates that request paths are not properly resolved, potentially exposing sensitive data. Users who rely on Envoy’s default file handling may be able to retrieve information they should not have access to if the proxy serves files based on the supplied path.

Affected Systems

The affected product is Envoy, the open‑source edge and service proxy. No specific version ranges are provided in the available data, so any released or deployed version of Envoy could be vulnerable until a vendor notice or patch confirms remediation. System administrators should review the Envoy version in use against the vendor’s advisories for confirmation.

Risk and Exploitability

The assessed CVSS score of 5.3 places the risk in a moderate category, and the vulnerability is listed as not a known exploited vulnerability in the CISA KEV database. Exploitation would likely occur over the network by crafting HTTP requests that include carefully structured dot/dot‑dot segments and parameters; the absence of EPSS data means the probability of active exploitation cannot be quantified. Attackers with network access to the Envoy instance could leverage this bypass to read ordinary files from the underlying filesystem, potentially compromising confidentiality. The impact is limited to file disclosure; there is no evidence of code execution or privilege escalation beyond unauthorized file access.

Generated by OpenCVE AI on September 1, 2026 at 14:09 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest security patch for Envoy when it becomes available.
  • Configure Envoy to disable or enforce strict path normalization, ensuring that dot and dot‑dot segments are not interpreted as directory traversal.
  • Implement access control or whitelisting for file serving paths, and monitor request logs for abnormal path patterns that may indicate traversal attempts.

Generated by OpenCVE AI on September 1, 2026 at 14:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 21 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Description No description is available for this CVE. 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.
Title envoy: envoy: path normalization bypass via dot/dot-dot segments with parameters Envoy: Path normalization does not handle dot and dotdot segments with parameters
Weaknesses CWE-647
References

Wed, 02 Sep 2026 22:15:00 +0000

Type Values Removed Values Added
First Time appeared Envoyproxy
Envoyproxy envoy
Vendors & Products Envoyproxy
Envoyproxy envoy

Tue, 01 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Description No description is available for this CVE.
Title envoy: envoy: path normalization bypass via dot/dot-dot segments with parameters
Weaknesses CWE-22
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate


Subscriptions

Envoyproxy Envoy
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-21T20:17:02.620Z

Reserved: 2026-08-12T20:53:46.380Z

Link: CVE-2026-73551

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-21T21:17:09.473

Modified: 2026-09-21T21:17:09.473

Link: CVE-2026-73551

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-26T13:00:00Z

Links: CVE-2026-73551 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-02T22:00:08Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-647

    Use of Non-Canonical URL Paths for Authorization Decisions