envoyproxy Envoy Gateway xDS Server Missing Authentication Exposes Control-Plane Data

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-53714?

CVE-2026-53714 is a vulnerability classified as Missing Authentication for Critical Functionality, affecting gateway (affected versions: < 1.7.4 and >= 1.8.0-rc.0, < 1.8.1). This vulnerability is rated High, with a CVSS score of 7.4. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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, the xDS gRPC server in GatewayNamespaceMode, configured through provider.kubernetes.deploy.type=GatewayNamespace, installs a JWT StreamInterceptor but no UnaryInterceptor, leaving every unary Fetch RPC unauthenticated. The streaming interceptor also authenticates only discoveryv3.DeltaDiscoveryRequest messages; a discoveryv3.DiscoveryRequest used by the State-of-the-World protocol fails the type assertion and returns success without JWT validation. Any pod that can reach port 18000 can use the unauthenticated unary or State-of-the-World paths to retrieve TLS private keys through StreamSecrets, all xDS resources through StreamAggregatedResources, backend endpoints through StreamClusters or StreamEndpoints, and routing configuration through StreamRoutes or StreamListeners. This issue is fixed in versions 1.7.4 and 1.8.1.

Affected products and scope

  • envoyproxy/gateway in GatewayNamespaceMode, configured with provider.kubernetes.deploy.type=GatewayNamespace, is affected at < 1.7.4.
  • The release branch >= 1.8.0-rc.0, < 1.8.1 is affected.
  • The confirmed fixes are 1.7.4 for the 1.7 branch and 1.8.1 for the 1.8 branch.
  • The record does not establish the status of branches or releases outside these stated ranges.

Technical details

In GatewayNamespaceMode, the Envoy Gateway xDS gRPC server is configured with a StreamInterceptor for JWT authentication but no UnaryInterceptor. As a result, the xDS server's unary Fetch RPCs do not perform authentication.

The streaming interceptor validates only messages of type discoveryv3.DeltaDiscoveryRequest. When the State-of-the-World protocol uses a discoveryv3.DiscoveryRequest, the type assertion fails and the processing path returns success without JWT validation.

Any pod that can reach port 18000 can access the unauthenticated paths to read TLS private keys through StreamSecrets, all xDS resources through StreamAggregatedResources, backend endpoints through StreamClusters or StreamEndpoints, and routing configuration through StreamRoutes or StreamListeners. The available evidence does not establish whether this port is exposed outside the cluster or how individual environments publish it.

Exploitability

The issue is reachable over the network by any pod that can connect to the xDS server on port 18000.

  • Valid credentials are not required for the affected unary or State-of-the-World paths.
  • No user interaction is required; the main precondition is network reachability to the xDS server.
  • The described attack path has low complexity and does not require prior privileges.
  • The normalized record marks public_exploit as false and provides no known-exploited status. This is record status, not proof that exploitation has never occurred.

Technical impact

The flaw permits unauthenticated reads from xDS, weakening the security boundary between any pod with network access and the Envoy control plane. An attacker can collect TLS private keys, configuration resources, backend endpoints, and routing information, creating a serious confidentiality risk.

The technical scope remains constrained by reachability to the xDS server on port 18000; the record does not establish that this port is reachable outside the cluster or only from an internal network. The supplied sources do not establish the ability to overwrite resources, change configuration, or cause availability loss.

Business impact

  • Sensitive-data exposure: TLS private keys can be read without authorization through StreamSecrets. If private keys are obtained, the organization may need to treat the related certificates as potentially compromised and replace them.
  • Infrastructure disclosure: xDS resources, backend endpoints, and routing configuration can reveal topology, internal services, and routing rules, supporting reconnaissance or targeted attacks.
  • Expanded trust boundary: A pod with network access to the xDS port can read control-plane data and managed Envoy information without the expected JWT authorization.
  • The available evidence describes read-oriented access paths and does not establish configuration modification or service disruption.

Remediation

  1. Upgrade the affected 1.7 branch to 1.7.4 or the affected 1.8 branch to 1.8.1, according to the deployed branch.
  2. After upgrading, verify that provider.kubernetes.deploy.type=GatewayNamespace is running a fixed release and that the xDS server requires JWT authentication for both unary and streaming RPCs.
  3. Until an upgrade is possible, temporarily restrict access to port 18000 to trusted control-plane and Envoy components. This reduces exposure but does not replace the fix.
  4. If unauthorized access to StreamSecrets cannot be ruled out, assess and replace the related TLS private keys and certificates.

Detection

  • Inventory envoyproxy Envoy Gateway deployments and identify environments using provider.kubernetes.deploy.type=GatewayNamespace.
  • Check Gateway versions against the branch-specific ranges in affected_summary; do not infer the status of branches that are not listed.
  • Verify the reachability of port 18000, especially from namespaces and pods outside the trusted control plane.
  • If gRPC or network-flow telemetry records method names, review requests to Fetch, StreamSecrets, StreamAggregatedResources, StreamClusters, StreamEndpoints, StreamRoutes, and StreamListeners.
  • Review access logs, audit logs, or interceptor telemetry for xDS requests without a valid JWT or without the expected authentication step. Absence of log evidence does not prove safety.
  • If unauthorized access to TLS private keys is possible, identify the related certificates and prepare to replace them.
Sources (26)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.