CVE-2026-53714: 
Wolfi vulnerability analysis and mitigation

CVE-2026-53714 is an authentication bypass vulnerability in Envoy Gateway's xDS gRPC server, classified as "xDS Control Plane Information Disclosure when Envoy Gateway operates in GatewayNamespaceMode." It 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), when configured with provider.kubernetes.deploy.type=GatewayNamespace. The vulnerability was disclosed on June 5, 2026 via a GitHub Security Advisory and has a CVSS v3.1 base score of 7.4 (High) (GitHub Advisory).

The root cause is CWE-306 (Missing Authentication for Critical Function): the xDS gRPC server in GatewayNamespaceMode registers a JWT StreamInterceptor but omits a UnaryInterceptor, leaving all unary Fetch RPCs completely unauthenticated. Additionally, the stream interceptor only validates tokens when the received message is of type discoveryv3.DeltaDiscoveryRequest; if a discoveryv3.DiscoveryRequest (used by the State-of-the-World/SotW xDS protocol) is received instead, the type assertion fails and RecvMsg returns nil (success) without any JWT validation — a classic fail-open authentication flaw. The fix, implemented in PR #8986, adds a Unary() interceptor and refactors the authenticate() method to handle both DeltaDiscoveryRequest and DiscoveryRequest message types via a shared extractNodeID() function (GitHub Advisory, Fix PR, Commit).

Any pod within the Kubernetes cluster that can reach the xDS server on port 18000 can exploit this vulnerability without credentials to retrieve highly sensitive control plane data. Exploitable resources include TLS private keys via StreamSecrets (SDS), all xDS resources via StreamAggregatedResources (ADS), backend service endpoints via StreamClusters/StreamEndpoints (CDS/EDS), and routing configuration via StreamRoutes/StreamListeners (RDS/LDS). Exposure of TLS private keys enables traffic decryption and man-in-the-middle attacks, while access to routing and endpoint data facilitates lateral movement and targeted attacks against backend services (GitHub Advisory).

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the time of this report. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and NVD's supplemental data indicates exploitation status as "none." The EPSS score is approximately 0.283%, reflecting a low near-term exploitation probability. However, the attack requires no privileges and no user interaction — only network adjacency (cluster-internal pod access to port 18000) — making it straightforward to exploit for any attacker with a foothold in the cluster (GitHub Advisory, Feedly).

1. Identify target: Confirm the Envoy Gateway deployment uses GatewayNamespaceMode (provider.kubernetes.deploy.type=GatewayNamespace) and is running a vulnerable version (< 1.7.4 or 1.8.0-rc.0 to < 1.8.1).
2. Gain cluster access: Obtain execution within any pod in the Kubernetes cluster that has network connectivity to the xDS gRPC server on port 18000 of the Envoy Gateway control plane.
3. Connect via unauthenticated unary RPC: Use a gRPC client (e.g., grpcurl or a custom Go/Python client) to call a unary Fetch RPC (e.g., FetchSecrets, FetchClusters) on port 18000 without providing any JWT token, exploiting the missing UnaryInterceptor.
4. Alternatively, use SotW streaming: Initiate a streaming RPC (e.g., StreamSecrets, StreamAggregatedResources) and send a discoveryv3.DiscoveryRequest message (SotW protocol) instead of a DeltaDiscoveryRequest; the type assertion in the interceptor fails and authentication is bypassed.
5. Retrieve sensitive data: Extract TLS private keys, backend endpoint addresses, routing rules, and other xDS configuration from the unauthenticated responses.
6. Leverage exfiltrated data: Use obtained TLS private keys to decrypt intercepted traffic, or use routing/endpoint data to identify and target internal backend services for further lateral movement (GitHub Advisory, Fix PR).

• Network: Unexpected or unauthorized gRPC connections to port 18000 on the Envoy Gateway control plane pod from pods that are not Envoy Proxy sidecars or known gateway components; unusual volume of xDS discovery requests from non-gateway pods.
• Logs: Envoy Gateway control plane logs showing StreamSecrets, StreamAggregatedResources, StreamClusters, StreamEndpoints, StreamRoutes, or StreamListeners RPC calls from unexpected client node IDs or IP addresses; absence of JWT validation log entries for connections that successfully retrieved xDS resources.
• Process/Behavior: gRPC client tools (e.g., grpcurl) or custom binaries executing within cluster pods and connecting to the xDS server port; pods making outbound connections to port 18000 that are not part of the expected Envoy Proxy fleet.

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 a UnaryInterceptor and fix the fail-open authentication logic in the stream interceptor to handle both DiscoveryRequest and DeltaDiscoveryRequest message types (GitHub Advisory, v1.7 Fix, v1.8 Fix). As a temporary workaround, restrict network access to port 18000 on the Envoy Gateway control plane using Kubernetes NetworkPolicies to allow connections only from authorized Envoy Proxy pods. Organizations not using GatewayNamespaceMode are not affected by this vulnerability.

The vulnerability was reported by researchers dashingDragon and Donjon-Cerberus, and the fix was developed by contributor cnvergence with rapid review and merge by the Envoy Gateway maintainer team. The fix PR received positive feedback from maintainers, with one noting "LGTM. Thanks for the quick fix!" The advisory was published by maintainer zirain on June 5, 2026 (GitHub Advisory, Fix PR).