github.com/envoyproxy/gateway
Affected
- introduced
1.8.0-rc.0, fixed1.8.1(semver)
Fixed versions
1.8.1
Fix
- Fixed version
1.8.1go get github.com/envoyproxy/[email protected]
Advisory
Also known as: BIT-envoy-gateway-2026-53714, CVE-2026-53714, GO-2026-6003
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. 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:
Credits
Envoy Gateway thanks @dashingDragon and @Donjon-Cerberus for reporting this issue.
High Basis: The source's own band: HIGH
1.8.0-rc.0, fixed 1.8.1 (semver)1.8.1
1.8.1go get github.com/envoyproxy/[email protected]0, fixed 1.7.4 (semver)1.7.4
1.7.4go get github.com/envoyproxy/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0