CVE-2026-53718
Published:September 14, 2026
Updated:September 22, 2026
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.
Affected Packages
github.com/envoyproxy/gateway (GO):
Affected version(s) >=latest <v1.7.4Fix Suggestion:
Update to version v1.7.4github.com/envoyproxy/gateway (GO):
Affected version(s) >=v0.1.0 <v1.7.4Fix Suggestion:
Update to version v1.7.4github.com/envoyproxy/gateway (GO):
Affected version(s) >=v1.8.0-rc.0 <v1.8.1Fix Suggestion:
Update to version v1.8.1Related Resources (10)
Do you need more information?
Contact UsCVSS v4
Base Score:
6.1
Attack Vector
NETWORK
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
LOW
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
6.4
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
LOW
Availability
LOW
Weakness Type (CWE)
Missing Authorization
EPSS
Base Score:
0.33