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.
CVE-2026-84445
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 49% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 51%
- KEV
- Not listed
Published
September 8, 2026
Last Modified
September 14, 2026
Advisory Details (10)
Auto-updated Sep 14, 2026Release 1.83.2
Patch available: grpc/grpc-go v1.83.2
https://github.com/grpc/grpc-go/releases/tag/v1.83.2Release 1.82.2
Patch available: grpc/grpc-go v1.82.2
https://github.com/grpc/grpc-go/releases/tag/v1.82.2commit 93e31b48545e (grpc/grpc-go)
Fix landed in grpc/grpc-go commit 93e31b48545e — awaiting tagged release
https://github.com/grpc/grpc-go/commit/93e31b48545e2a8aaeb6e06b47fb249f94e6297fcommit 8668b69c167d (grpc/grpc-go)
Patch available: grpc/grpc-go v1.83.2 (contains commit 8668b69c167d)
https://github.com/grpc/grpc-go/commit/8668b69c167df908b6b3666dcbf40992b9e932a4commit 3822494d8ea0 (grpc/grpc-go)
Patch available: grpc/grpc-go v1.82.2 (contains commit 3822494d8ea0)
https://github.com/grpc/grpc-go/commit/3822494d8ea03b992c089fd2a195f041762fffb7cherry-pick #9365 to v1.82.x
Patch available: grpc/grpc-go v1.82.2 (PR #9367 merged 2026-08-25)
https://github.com/grpc/grpc-go/pull/9367cherry-pick #9365 to v1.83.x
Patch available: grpc/grpc-go v1.83.2 (PR #9366 merged 2026-08-25)
https://github.com/grpc/grpc-go/pull/9366transport: reject requests missing :authority and host headers
Fix merged in grpc/grpc-go PR #9365 on 2026-08-25 — awaiting tagged release
https://github.com/grpc/grpc-go/pull/9365xds: server crashes with 'index out of range' when a request omits :authority · Issue #9354 · grpc/grpc-go · GitHub
https://github.com/grpc/grpc-go/issues/9354Denial of Service (DoS) via crash due to missing `:authority` and `Host` headers in gRPC-Go xDS servers · Advisory · grpc/grpc-go · GitHub
https://github.com/grpc/grpc-go/security/advisories/GHSA-2v4p-qf9q-27wjVendor Advisories for CVE-2026-84445(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| google.golang.org/grpc | — | 1.85.0-dev.0.20260825072537-93e31b48545e | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 15× in last 7d / 16× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 07:46 UTCVendor advisory
- 2026-09-18 19:55 UTCEG score recompute
- 2026-09-18 19:55 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 08:05 UTCVendor advisory
- 2026-09-17 20:16 UTCEG score recompute
- 2026-09-17 20:16 UTCVendor advisory
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 18:15 UTCEG score recompute
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 17:28 UTCEG score recompute
- 2026-09-14 16:45 UTCEG score recompute
- 2026-09-14 16:20 UTCEG score recompute▲ 8.70
- 2026-09-14 16:19 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7
- 2026-09-08 21:36 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-129 · CWE-248
Frequently asked(5)
What is CVE-2026-84445?
When was CVE-2026-84445 disclosed?
Is CVE-2026-84445 actively exploited?
What is the CVSS score of CVE-2026-84445?
How do I remediate CVE-2026-84445?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84445
Is Your Infrastructure Affected by CVE-2026-84445?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.