CVE-2026-53718
Description
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.
How to fix
- github.com/envoyproxy/gateway1.8.1, 1.7.4 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| github.com/envoyproxy/gatewayGo | 1.8.0-rc.0 ≤ v < 1.8.1, v < 1.7.4 | 1.8.1, 1.7.4 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.