CVE-2026-53718
Published:July 16, 2026
Updated:August 02, 2026
Impact Envoy Gateway accepts extension-managed custom backendRefs from an HTTPRoute to a backend resource in another namespace without requiring a matching Gateway API ReferenceGrant in the target namespace. This breaks the Gateway API cross-namespace consent model: the namespace that owns the referenced backend resource does not need to opt in with a ReferenceGrant before another namespace’s HTTPRoute can use that resource. Patches "1.7.4" (https://github.com/envoyproxy/gateway/releases/tag/v1.7.4) "1.8.1" (https://github.com/envoyproxy/gateway/releases/tag/v1.8.1)
Affected Packages
github.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 (2)
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