gRPC-Go: Denial of Service (DoS) via crash due to missing `:authority` and `Host` headers in the xDS servers
grpc-go
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| google.golang.org/grpc Go |
|
|
grpc-go
| Product | Affected | Fixed in |
|---|---|---|
| google.golang.org/grpc Go |
|
|
1.85.0-dev.0.20260825072537-93e31b48545egRPC-Go is the Go language implementation of gRPC. Prior to 1.82.2 and 1.83.2, servers created with xds.NewGRPCServer() allow internal/transport/http2_server.go to accept an RPC containing neither the :authority header nor the Host header, while RouteAndProcess in internal/xds/server/routing.go assumes that an authority value exists and indexes the empty slice. A remote client that can complete transport connection establishment can trigger an index-out-of-bounds panic that is not recovered by the per-RPC goroutine and terminates the entire server process. In insecure or ordinary TLS deployments the request can be unauthenticated, while strict mTLS or ALTS deployments require valid transport credentials before the malformed RPC can reach the interceptor. This issue is fixed in versions 1.82.2 and 1.83.2.
From the CVE record · GitHub_M
grpc-go servers created with xds.NewGRPCServer() can panic and terminate when an RPC contains neither an :authority nor a Host header. A remote client that establishes a transport connection can trigger this; the request can be unauthenticated with insecure or ordinary TLS, while strict mTLS or ALTS requires valid transport credentials.
Engineers running xds.NewGRPCServer() with google.golang.org/grpc versions <1.82.2, >=1.83.0 <1.83.2, or the listed affected 1.84.0-dev and 1.85.0-dev builds should check their deployments.