CVE-2026-53714: Envoy Gateway: xDS Control Plane Information Disclosure when operating in GatewayNamespaceMode
Impact When Envoy Gateway runs in GatewayNamespaceMode (provider.kubernetes.deploy.type=GatewayNamespace), the xDS gRPC server is configured with a StreamInterceptor for JWT authentication but no UnaryInterceptor. The go-control-plane xDS server exposes both streaming and unary (Fetch) RPC methods for all registered discovery services.
Published Jul 16, 2026
Affected packages
github.com/envoyproxy/gateway
- Ecosystem
- Go
- Affected
- >= 1.8.0-rc.0, < 1.8.1
- Fixed in
- 1.8.1
- Check
go list -m github.com/envoyproxy/gateway
github.com/envoyproxy/gateway
- Ecosystem
- Go
- Affected
- < 1.7.4
- Fixed in
- 1.7.4
- Check
go list -m github.com/envoyproxy/gateway
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
When Envoy Gateway runs in GatewayNamespaceMode (provider.kubernetes.deploy.type=GatewayNamespace), the xDS gRPC server is configured with a StreamInterceptor for JWT authentication but no UnaryInterceptor. The go-control-plane xDS server exposes both streaming and unary (Fetch) RPC methods for all registered discovery services. Since there is no unary interceptor, these Fetch endpoints are completely unauthenticated.
Additionally, the JWT authentication interceptor in GatewayNamespaceMode only validates tokens when the received gRPC message is of type discoveryv3.DeltaDiscoveryRequest . If the message is a discoveryv3.DiscoveryRequest — used by the State-of-the-World (SotW) xDS protocol — the type assertion fails, the validation block is skipped entirely, and RecvMsg returns nil (success) without any authentication.
Any pod in the cluster that can reach the xDS server (port 18000) can use the SotW protocol to bypass JWT authentication and access:
- TLS private keys via StreamSecrets (SDS)
- All xDS resources via StreamAggregatedResources (ADS)
- Backend endpoints via StreamClusters / StreamEndpoints (CDS/EDS)
- Routing rules via StreamRoutes / StreamListeners (RDS/LDS)
Credits
Envoy Gateway thanks @dashingDragon and @Donjon-Cerberus for reporting this issue.
Credited to cnvergence, zirain, guydc, dashingDragon.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-53713
Envoy Gateway: Authentication Bypass via Improper Input Validation in EnvoyExtensionPolicy Lua Allows Secret Disclosure
critical9.1Jul 16, 2026CVE-2026-53715
Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock
medium5.3Jul 16, 2026CVE-2026-53716
Envoy Gateway: Wasm HTTP fetch decompresses gzip without output-size limit
medium6.5Jul 16, 2026CVE-2026-53717
Envoy Gateway: OCI layer extraction allocates make([]byte, h.Size) from untrusted tar header
medium6.5Jul 16, 2026CVE-2026-53718
Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass
medium6.4Jul 16, 2026CVE-2026-53719
Envoy Gateway: Nil-dereference when SecurityPolicy targets TCPRoute without spec.authorization
medium6.5Jul 16, 2026
