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 normally matches the raw request path, while servlet backends such as Apache Tomcat strip semicolon matrix parameters from each path segment before resolving the resource. Envoy's ignore_path_parameters_in_path_matching option instead truncates at the first semicolon and still does not match per-segment backend behavior. A remote client can use a parameterized protected segment, or a parameter on an earlier segment, to make Envoy select an unprotected fallback while the backend resolves the protected resource. The relevant scope boundary is that the bypass requires both a path-based Envoy decision and a backend that strips semicolon parameters per segment. 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: Potential Authentication Bypass
Action: Assess
AI Analysis

Impact

The path matching bypass in Envoy’s router allows an actor to craft URLs that include per‑segment parameters not stripped during routing, which may cause the router to match a request to an unintended route. This flaw, classified under CWE‑289 and CWE‑436, could potentially enable an attacker to bypass authentication or authorization controls by reaching protected endpoints that should be inaccessible. The documented impact is an elevation of privilege that could expose sensitive data or services.

Affected Systems

The vulnerability targets the Envoy proxy server. No specific affected versions are listed in the available data, so any deployment that has not verified its patch status should be treated as potentially vulnerable.

Risk and Exploitability

The CVSS score of 5.3 points to a moderate severity. The EPSS score is not available and the flaw is not listed in the CISA KEV catalog, indicating no confirmed exploits to date. It is most likely exploitable over the network when an attacker submits a crafted request to an Envoy‑managed service. Because the flaw revolves around request origin verification, the attack vector can be performed by any party that can reach the Envoy instance over the network.

Generated by OpenCVE AI on September 21, 2026 at 21:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Envoy to the latest stable release where the path matching bypass is addressed.
  • If an upgrade is not feasible, modify the Envoy configuration to strip per‑segment parameters or disable unsafe routing options.
  • Restrict access to the Envoy ingress endpoints to trusted networks or enforce TLS client authentication.

Generated by OpenCVE AI on September 21, 2026 at 21:35 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 normally matches the raw request path, while servlet backends such as Apache Tomcat strip semicolon matrix parameters from each path segment before resolving the resource. Envoy's ignore_path_parameters_in_path_matching option instead truncates at the first semicolon and still does not match per-segment backend behavior. A remote client can use a parameterized protected segment, or a parameter on an earlier segment, to make Envoy select an unprotected fallback while the backend resolves the protected resource. The relevant scope boundary is that the bypass requires both a path-based Envoy decision and a backend that strips semicolon parameters per segment. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Title envoy: envoy: path matching bypass via per-segment parameters not stripped by router Envoy: Potential path-matching/authentication bypass when using Envoy in combination with a backend stripping per-segment path (matrix) parameters (e.g. Apache Tomcat)
Weaknesses CWE-289
CWE-436
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 matching bypass via per-segment parameters not stripped by router
Weaknesses CWE-706
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:20:26.487Z

Reserved: 2026-08-12T19:00:33.736Z

Link: CVE-2026-73511

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

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

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

Link: CVE-2026-73511

cve-icon Redhat

Severity : Moderate

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

Links: CVE-2026-73511 - Bugzilla

cve-icon OpenCVE Enrichment

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

Weaknesses
  • CWE-289

    Authentication Bypass by Alternate Name

  • CWE-436

    Interpretation Conflict

  • CWE-706

    Use of Incorrectly-Resolved Name or Reference