GHSA-2v4p-qf9q-27wj

Suggest an improvement
Source
https://github.com/advisories/GHSA-2v4p-qf9q-27wj
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-2v4p-qf9q-27wj/GHSA-2v4p-qf9q-27wj.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-2v4p-qf9q-27wj
Aliases
  • CVE-2026-84445
Downstream
Published
2026-09-08T21:21:43Z
Modified
2026-09-08T21:40:56Z
Summary
gRPC-Go xDS servers: Denial of Service (DoS) via crash due to missing `:authority` and `Host` headers
Details

A vulnerability exists in gRPC-Go servers configured with xds.NewGRPCServer() where a crafted request missing both :authority and Host headers can cause a server panic, resulting in a Denial of Service (DoS).

Servers built with xds.NewGRPCServer install an xDS routing interceptor on every RPC. This interceptor looks up the request’s :authority header to pick a virtual host. The HTTP/2 server transport previously accepted requests that had neither :authority nor Host. When this happened, the xDS routing interceptor attempted to access the first element of an empty slice of authorities, leading to an index out of bounds panic. Since the per-RPC goroutine does not recover from panics, the entire server process would terminate.

This panic occurs in the interceptor pipeline, meaning the transport credentials handshake (TLS, mTLS, or ALTS) and HTTP/2 connection establishment must complete successfully before the crafted request can reach this logic.

  • Insecure/Standard TLS: If the server permits insecure (plaintext) connections or standard credentials (where client certs are not checked), any unauthenticated remote attacker can trigger the crash.
  • mTLS / ALTS: If strict transport-level authentication is enforced at the network edge or transport layer (e.g., requiring a valid client certificate), the attacker must possess valid transport credentials to initiate the stream and trigger the panic.

Impact

An attacker can cause a complete outage of the gRPC server by sending a request missing both :authority and Host headers, provided they can successfully establish a transport connection.

Patches

The issue has been addressed in master (and backported to 1.83.2 and 1.82.2). The fix updates the HTTP/2 transport layer to reject requests missing both :authority and Host headers early, maintaining consistency with and other gRPC language implementations.

Database specific
{
    "cwe_ids": [
        "CWE-129",
        "CWE-248"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-08T21:21:43Z",
    "nvd_published_at": null,
    "severity": "HIGH"
}
References

Affected packages

Go / google.golang.org/grpc

Package

Name
google.golang.org/grpc
View open source insights on deps.dev
Purl
pkg:golang/google.golang.org/grpc

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
1.82.2

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-2v4p-qf9q-27wj/GHSA-2v4p-qf9q-27wj.json"

Go / google.golang.org/grpc

Package

Name
google.golang.org/grpc
View open source insights on deps.dev
Purl
pkg:golang/google.golang.org/grpc

Affected ranges

Type
SEMVER
Events
Introduced
1.83.0
Fixed
1.83.2

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-2v4p-qf9q-27wj/GHSA-2v4p-qf9q-27wj.json"

Go / google.golang.org/grpc

Package

Name
google.golang.org/grpc
View open source insights on deps.dev
Purl
pkg:golang/google.golang.org/grpc

Affected ranges

Type
SEMVER
Events
Introduced
1.84.0-dev
Fixed
1.85.0-dev.0.20260825072537-93e31b48545e

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-2v4p-qf9q-27wj/GHSA-2v4p-qf9q-27wj.json"