Answer in brief
CVE-2026-53714 records a High severity (CVSS 7.4) vulnerability in Envoy Gateway: xDS Control Plane Information Disclosure when Envoy Gateway operates in GatewayNamespaceMode. The current sources do not mark it as known exploited. The current feed maps envoyproxy/gateway (generic), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps envoyproxy/gateway (generic), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| envoyproxy/gatewaygeneric | < 1.7.4 || >= 1.8.0-rc.0, < 1.8.1 | Not reported |
| github.com/envoyproxy/gatewaygo | >=1.8.0-rc.0,<1.8.1 | 1.8.1 |
| github.com/envoyproxy/gatewaygo | <1.7.4 | 1.7.4 |
| github.com/envoyproxy/gatewaygo | >=1.8.0-rc.0 <1.8.1 | 1.8.1 |
| github.com/envoyproxy/gatewaygo | >=0 <1.7.4 | 1.7.4 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 16, 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, 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.
Quoted source text, attributed separately from HOL analysis.