CVE-2026-73511Envoy: Potential path-matching/authentication bypass when using Envoy in combination with a backend stripping per-segment path (matrix) parameters (e.g. Apache Tomcat)
Updated under an hour ago ()
Does this affect you?
It affects envoyproxy envoy. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 5.3 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Weakness (CWE)
- CWE-289, CWE-436
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Analyzed
- Record last updated
- Sep 22, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
envoyproxy envoy envoyproxy:envoy (from the name) | before 1.36.10; from 1.37.0, < 1.37.6; from 1.38.0, < 1.38.4; from 1.39.0, < 1.39.1 | CNA record |
envoyproxy envoy envoyproxy:envoy | before 1.36.10; from 1.37.0 before 1.37.6; from 1.38.0 before 1.38.4; from 1.39.0 before 1.39.1 | NVD |
References
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-m745-gh6x-349xx-refsource-confirm, exploit, vendor-advisory
- https://github.com/envoyproxy/envoy/commit/26d5x-refsource-misc, patch
- https://github.com/envoyproxy/envoy/commit/50f7bfa48dccfee339822e9846b2b8053e07d325x-refsource-misc, patch
- https://github.com/envoyproxy/envoy/commit/b205d1f4982e14ce5693ba94ef84d37e7155e050x-refsource-misc, patch
- https://github.com/envoyproxy/envoy/commit/fcb663752c7055257f5dcc8b6ce6c7c905ebb1ffx-refsource-misc, patch
- https://github.com/envoyproxy/envoy/releases/tag/v1.36.10x-refsource-misc, release-notes
- https://github.com/envoyproxy/envoy/releases/tag/v1.37.6x-refsource-misc, release-notes
- https://github.com/envoyproxy/envoy/releases/tag/v1.38.4x-refsource-misc, release-notes
- https://github.com/envoyproxy/envoy/releases/tag/v1.39.1x-refsource-misc, release-notes
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.