CVE-2026-73553: envoyproxy envoy · Interpretation Conflict
Affects envoyproxy envoySource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 1.39.1 : patch envoyproxy envoy soon.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.39.1, 1.38.4, 1.37.6 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade envoy and envoyproxy/envoy to 1.39.1, 1.38.4, 1.37.6 or 1.36.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
GitHubenvoyproxy/envoypkg:github/envoyproxy/envoyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Envoy versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1. Users should upgrade to these or later versions to remediate the issue. No other mitigation steps are indicated by the vendor advisory.
Description
Envoy proxy versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 contain a vulnerability where inconsistent path canonicalization allows bypassing path-based authorization. When the ignore_path_parameters_in_path_matching option is enabled, the router strips semicolon suffixes before matching, but the RBAC url_path matcher evaluates the raw path. This discrepancy can let unauthenticated clients bypass DENY rules on protected routes. The issue is fixed in the specified versions.
References
- github.com/envoyproxy/envoy/security/advisories/GHSA-77x5-xqjg-hprq (opens in a new tab)
- github.com/envoyproxy/envoy/commit/0be4a0302ea94a894e470817c2edfbd5ed90d273 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/6a703a375a20e3bf98140ee5f5522c614adee7b6 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/b6ec9b66cc33a415e2fa81a6fa8363cac4772dd1 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/e6d5fe885409ebb335ed3934a167f0bcfea471f2 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.36.10 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.37.6 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.38.4 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.39.1 (opens in a new tab)