CVSS 3.1
6.4 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:LCVE-2026-53718
Medium (6.4). EPSS 0.4% chance of exploitation in the next 30 days. Fixed in github.com/envoyproxy/gateway 1.7.4, 1.8.1.
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, an HTTPRoute can use an extension-managed custom backendRef to reference a backend resource in another namespace without a matching Gateway API ReferenceGrant in the target namespace. The custom-backend branch in internal/gatewayapi/route.go omits validateBackendNamespace, allowing the route-owning namespace to bind to and use the resource without the backend namespace owner's consent and violating the Gateway API cross-namespace authorization model. This issue is fixed in versions 1.7.4 and 1.8.1.
Severity
- EPSS
- 0.4% chance of exploitation in the next 30 days; higher than 35% of CVEs (scores of 2026-10-31)
- CWE
- CWE-862
- Published
- Modified
- Record from
- the NVD, synced
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-fcrp-7gc2-93g7 | Go | github.com/envoyproxy/gateway | >=1.8.0-rc.0 <1.8.1 | 1.8.1 |
| GHSA-fcrp-7gc2-93g7 | Go | github.com/envoyproxy/gateway | <1.7.4 | 1.7.4 |
| GO-2026-6007 | Go | github.com/envoyproxy/gateway | <1.7.4 >=1.8.0-rc.0 <1.8.1 | 1.7.4, 1.8.1 |
References
- https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464
- https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7
- https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead
- https://github.com/envoyproxy/gateway/pull/9171
- https://github.com/envoyproxy/gateway/pull/9172