Live › vulnerability › CVE-2026-84445
Go to dashboardgRPC-Go servers created with xds.NewGRPCServer() can be crashed by an RPC that carries neither an :authority nor a Host header, because the routing code indexes an empty slice. A remote client that can establish a transport connection can take down the entire server process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| google.golang.org/grpc | go | >= 1.85.0-dev, < 1.85.0-dev.0.20260825072537-93e31b48545e | 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e |
Search the codebase for xds.NewGRPCServer() and check google.golang.org/grpc in go.mod or go.sum for a version below 1.82.2 or 1.83.2.
Upgrade google.golang.org/grpc to 1.82.2 or 1.83.2 (or a later release that includes the fix).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
gRPC-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.
This page as .md · .json · in your agent: get_signal("CVE-2026-84445")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.