CVE-2026-73511
CVE-2026-73511 is a medium-severity vulnerability in Envoyproxy Envoy with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-289.
Key facts
- Severity: Medium (CVSS 3.x base score 5.3)
- EPSS exploit prediction: 0% (29th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-289
- Affected product: Envoyproxy Envoy
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-73511?
- 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.
- How severe is CVE-2026-73511?
- CVE-2026-73511 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
- Is CVE-2026-73511 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-73511?
- CVE-2026-73511 affects Envoyproxy Envoy. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-73511?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2026-73511 published?
- CVE-2026-73511 was published on 2026-09-21 and last updated on 2026-10-05.
References
- https://github.com/envoyproxy/envoy/commit/26d5
- https://github.com/envoyproxy/envoy/commit/50f7bfa48dccfee339822e9846b2b8053e07d325
- https://github.com/envoyproxy/envoy/commit/b205d1f4982e14ce5693ba94ef84d37e7155e050
- https://github.com/envoyproxy/envoy/commit/fcb663752c7055257f5dcc8b6ce6c7c905ebb1ff
- https://github.com/envoyproxy/envoy/releases/tag/v1.36.10
- https://github.com/envoyproxy/envoy/releases/tag/v1.37.6
- https://github.com/envoyproxy/envoy/releases/tag/v1.38.4
- https://github.com/envoyproxy/envoy/releases/tag/v1.39.1
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-m745-gh6x-349x
Affected products (1)
- cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
More vulnerabilities in Envoyproxy Envoy
- CVE-2022-29226 — Critical (CVSS 10.0): Envoy is a cloud-native high-performance proxy. In versions prior to 1.22.1 the OAuth filter implementation does not…
- CVE-2019-18802 — Critical (CVSS 9.8): An issue was discovered in Envoy 1.12.0. An untrusted remote client may send an HTTP header (such as Host) with…
- CVE-2019-18801 — Critical (CVSS 9.8): An issue was discovered in Envoy 1.12.0. An untrusted remote client may send HTTP/2 requests that write to the heap…
- CVE-2020-35470 — High (CVSS 8.8): Envoy before 1.16.1 logs an incorrect downstream address because it considers only the directly connected peer, not the…
- CVE-2024-23324 — High (CVSS 8.6): Envoy is a high-performance edge/middle/service proxy. External authentication can be bypassed by downstream…
- CVE-2023-35941 — High (CVSS 8.6): Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to versions 1.27.0,…
All CVEs affecting Envoyproxy Envoy →
Other CWE-289 vulnerabilities
- CVE-2026-76183 — Critical (CVSS 9.8): Authentication Bypass by Alternate Name vulnerability in Apache Tomcat allowed the security constraints for any…
- CVE-2026-15980 — Critical (CVSS 9.8): The MyHome Core plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including,…
- CVE-2026-8457 — Critical (CVSS 9.8): The WooCommerce - Social Login plugin for WordPress is vulnerable to Authentication Bypass in all versions up to and…
- CVE-2026-9701 — Critical (CVSS 9.8): The Eventer plugin for WordPress is vulnerable to an insecure password reset mechanism in all versions up to, and…
- CVE-2026-24058 — Critical (CVSS 9.8): Soft Serve is a self-hostable Git server for the command line. Versions 0.11.2 and below have a critical authentication…
- CVE-2025-13613 — Critical (CVSS 9.8): The Elated Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including,…