envoy: Interpretation Conflict
CVE-2026-73553 is a high-severity interpretation conflict vulnerability in envoy from Envoyproxy, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected envoy versions: < 1.36.10; >= 1.37.0, < 1.37.6; >= 1.38.0, < 1.38.4, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.51% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of envoy you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Envoyproxy | envoy | < 1.36.10; >= 1.37.0, < 1.37.6; >= 1.38.0, < 1.38.4; >= 1.39.0, < 1.39.1 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N. Scored by CNA (github.com).
Official 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, When ignore_path_parameters_in_path_matching is enabled, Envoy's router strips the semicolon suffix before matching but the RBAC url_path matcher evaluates the raw path. A downstream request such as /admin;x can therefore miss a DENY rule for /admin while the router still selects the protected /admin backend. The inconsistent canonicalization allows an unauthenticated client to bypass path-based authorization. The relevant scope boundary is that the route option and a path-based RBAC rule must both be present, and the protected route must match after stripping. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Interpretation Conflict
Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/envoyproxy/envoy/security/advisories/GHSA-77x5-xqjg-hprqExploit, Mitigation
Patches and release notes
- github.com/envoyproxy/envoy/commit/0be4a0302ea94a894e470817c2edfbd5ed90d273
- github.com/envoyproxy/envoy/commit/6a703a375a20e3bf98140ee5f5522c614adee7b6
- github.com/envoyproxy/envoy/commit/b6ec9b66cc33a415e2fa81a6fa8363cac4772dd1
- github.com/envoyproxy/envoy/commit/e6d5fe885409ebb335ed3934a167f0bcfea471f2
- github.com/envoyproxy/envoy/releases/tag/v1.36.10Release Notes
- github.com/envoyproxy/envoy/releases/tag/v1.37.6Release Notes
- github.com/envoyproxy/envoy/releases/tag/v1.38.4Release Notes
- github.com/envoyproxy/envoy/releases/tag/v1.39.1Release Notes
Other vulnerabilities in envoy
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.4 High severity
- 7.5 High severity
Recent Interpretation Conflict vulnerabilities
- 7.4 High severity
- 8.8 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 9.4 Critical severity
Spotted an error? Tell us.