Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-84445

Vulnerability in google.golang.org/grpc (CVE-2026-84445)

Summary

Vulnerability in google.golang.org/grpc (CVE-2026-84445). Risk of unauthorized operations or information disclosure. Exploitable via Host. Mitigation: upgrade to 1.85.0-dev.0.20260825072537-93e31b48545e or later.

Original description

The description as published by the source.

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 b…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-84445 has been found in google.golang.org/grpc.
Attackers can target a specific entry point like Host over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade google.golang.org/grpc to 1.85.0-dev.0.20260825072537-93e31b48545e or later.
If unsure, ask your IT team or search "google.golang.org/grpc CVE-2026-84445" on the vendor's site.

CVE-2026-84445 (google.golang.org/grpc) — CWE-129
Attack surface: Host / xds.NewGRPCServer / master
Patched: 1.85.0-dev.0.20260825072537-93e31b48545e — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-129) exists in google.golang.org/grpc. Attackers reach the vulnerable code path via Host.

📍 Affected scope

Check the vendor advisory for the affected versions of google.golang.org/grpc. Attack surface: Host / xds.NewGRPCServer / master.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.85.0-dev.0.20260825072537-93e31b48545e.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'google.golang.org/grpc' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'google.golang.org/grpc' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で google.golang.org/grpc を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade google.golang.org/grpc to 1.85.0-dev.0.20260825072537-93e31b48545e

    ステージング環境で 1.85.0-dev.0.20260825072537-93e31b48545e に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go google.golang.org/grpc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.85.0-dev.0.20260825072537-93e31b48545e"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details