CVE-2026-53718: 
Wolfi vulnerability analysis and mitigation

CVE-2026-53718 is a missing authorization vulnerability in Envoy Gateway that allows an HTTPRoute to reference a backend resource in another Kubernetes namespace without a matching Gateway API ReferenceGrant in the target namespace. This breaks the Gateway API cross-namespace consent model, enabling a route-owning namespace to bind to and use backend resources without the backend namespace owner's approval. The vulnerability affects Envoy Gateway versions prior to 1.7.4 and versions 1.8.0-rc.0 through 1.8.0 (prior to 1.8.1). It was disclosed on June 5, 2026, and carries a CVSS v3.1 base score of 6.4 (Medium) (GitHub Advisory).

The root cause is classified as CWE-862 (Missing Authorization). In internal/gatewayapi/route.go, the processDestination function's custom-backend branch omits a call to validateBackendNamespace, which is responsible for checking whether a matching ReferenceGrant exists in the target namespace before allowing cross-namespace backend references. The fix adds an else branch that explicitly invokes validateBackendNamespace for custom backend resources, enforcing the same ReferenceGrant requirement applied to standard backends. Exploitation requires network access and low-level privileges (e.g., the ability to create or modify HTTPRoute resources in a Kubernetes cluster), and attack complexity is rated High due to the specific configuration conditions required (GitHub Advisory, Fix PR #9173).

A tenant or user with permission to create HTTPRoutes in one namespace can route traffic through extension-managed custom backend resources in other namespaces without the consent of those namespaces' owners. This can result in unauthorized access to sensitive backend services (high confidentiality impact), limited data manipulation (low integrity impact), and potential disruption of backend availability (low availability impact). In multi-tenant Kubernetes environments, this effectively breaks namespace isolation for custom backend types managed by gateway extensions (GitHub Advisory).

No public proof-of-concept exploit code or in-the-wild exploitation has been reported for this vulnerability. The NVD SSVC assessment classifies exploitation as "none" and the vulnerability as not automatable. The EPSS score is approximately 0.327%, indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (GitHub Advisory, Feedly).

1. Identify target environment: Confirm the target Kubernetes cluster is running Envoy Gateway version < 1.7.4 or 1.8.0-rc.0 to < 1.8.1 with at least one gateway extension that manages custom backendRef types.
2. Obtain route creation privileges: Acquire credentials or a service account with permission to create or modify HTTPRoute resources in a namespace (low-privilege access is sufficient).
3. Identify target backend: Enumerate backend resources (e.g., custom types like S3Backend) in other namespaces that the attacker wishes to access but for which no ReferenceGrant has been granted to the attacker's namespace.
4. Craft malicious HTTPRoute: Create an HTTPRoute in the attacker-controlled namespace with a backendRef pointing to the custom backend resource in the target namespace, specifying the correct group, kind, name, and namespace fields.
5. Traffic interception: Once Envoy Gateway processes the route (without enforcing ReferenceGrant validation for custom backends), traffic matching the HTTPRoute rules will be forwarded to the unauthorized backend resource, potentially exposing sensitive data or services (GitHub Advisory, Fix PR #9173).

• Kubernetes API Audit Logs: HTTPRoute creation or update events in a namespace where the backendRef references a resource in a different namespace, without a corresponding ReferenceGrant in the target namespace.
• Envoy Gateway Controller Logs: Absence of RefNotPermitted condition or error messages for cross-namespace custom backend references in affected versions; presence of such messages after patching indicates the fix is active.
• Kubernetes Resource Inspection: HTTPRoute objects with backendRef entries specifying a namespace field different from the route's own namespace and using a non-standard group/kind (custom backend type), without a matching ReferenceGrant in the target namespace.
• Network Traffic: Unexpected traffic flows from Envoy proxy pods to backend services in namespaces that have not explicitly granted access via ReferenceGrant (GitHub Advisory).

Upgrade Envoy Gateway to version 1.7.4 (for the 1.7.x branch) or 1.8.1 (for the 1.8.x branch), which add the missing validateBackendNamespace call for custom backend references. No configuration-based workaround is documented by the vendor; upgrading to a patched version is the recommended remediation. As an interim measure, administrators can audit existing HTTPRoutes for cross-namespace custom backend references and manually verify or enforce ReferenceGrant policies (GitHub Advisory, v1.7.4 Release, v1.8.1 Release).