CVE-2026-84445

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-77627 (ENISA EUVD) · GHSA-2v4p-qf9q-27wj (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 8, 2026

Last Modified

September 25, 2026

Advisory Details (10)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Release 1.83.2

Patch available: grpc/grpc-go v1.83.2

https://github.com/grpc/grpc-go/releases/tag/v1.83.2
GitHub release Patch Available

Release 1.82.2

Patch available: grpc/grpc-go v1.82.2

https://github.com/grpc/grpc-go/releases/tag/v1.82.2
GitHub commit

commit 93e31b48545e (grpc/grpc-go)

Fix landed in grpc/grpc-go commit 93e31b48545e — awaiting tagged release

https://github.com/grpc/grpc-go/commit/93e31b48545e2a8aaeb6e06b47fb249f94e6297f
GitHub commit Patch Available

commit 8668b69c167d (grpc/grpc-go)

Patch available: grpc/grpc-go v1.83.2 (contains commit 8668b69c167d)

https://github.com/grpc/grpc-go/commit/8668b69c167df908b6b3666dcbf40992b9e932a4
GitHub commit Patch Available

commit 3822494d8ea0 (grpc/grpc-go)

Patch available: grpc/grpc-go v1.82.2 (contains commit 3822494d8ea0)

https://github.com/grpc/grpc-go/commit/3822494d8ea03b992c089fd2a195f041762fffb7
GitHub pull request Patch Available

cherry-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/9367
GitHub pull request Patch Available

cherry-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/9366
GitHub pull request

transport: 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/9365
Web page

xds: 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/9354
GitHub advisoryMentions a patch (unverified)

Denial 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-27wj

Patch Availability(34)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-builds/openshift-builds-webhook-rhel10:17926809442026-10-24redhat
redhatopenshift-builds/openshift-builds-webhook-rhel9:17927433292026-10-24redhat
redhatopenshift-builds/openshift-builds-webhook-rhel10:17928355712026-10-24redhat
redhatopenshift-builds/openshift-builds-webhook-rhel9:17928518952026-10-24redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17918163162026-10-21redhat
redhatrhoai/odh-trustyai-service-operator-rhel9:17918707732026-10-21redhat
redhatrhmtc/openshift-migration-velero-plugin-for-mtc-rhel8:17918543572026-10-20redhat
redhatdevworkspace/devworkspace-rhel9-operator:17913686652026-10-19redhat
redhatrhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9:17918325382026-10-19redhat
redhatmigration-toolkit-virtualization/mtv-validation-rhel9:17912282472026-10-15redhat
redhatrhtas/updatetree-rhel9:17915499562026-10-15redhat
redhatrhtas/rekor-monitor-rhel9:17915352782026-10-15redhat
redhatmigration-toolkit-virtualization/mtv-validation-rhel9:17912290312026-10-15redhat
redhatrhtas/createtree-rhel9:17915499562026-10-15redhat
redhatrhtas/trillian-logsigner-rhel9:17915499562026-10-15redhat
redhatrhtas/policy-controller-rhel9:17918131242026-10-15redhat
redhatopenshift-logging/lokistack-gateway-rhel9:17915008642026-10-14redhat
redhatcert-manager/cert-manager-operator-rhel9:17917882872026-10-13redhat
redhatopentelemetry-collector-0:0.158.0-1.el10_02026-10-13redhat
redhatopentelemetry-collector-0:0.158.0-1.el9_62026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17913710692026-10-13redhat
redhatopentelemetry-collector-0:0.158.0-1.el9_42026-10-13redhat
redhatrhc-1:0.2.7-1.el9_6.72026-10-08redhat
redhatrhosdt/tempo-rhel9-operator:17914525622026-10-08redhat
redhathelm-cli/helm-cli-rhel9:17897192772026-10-08redhat
redhatopentelemetry-collector-0:0.158.0-1.el9_82026-10-08redhat
redhatrhdh/rhdh-rhel9-operator:17912196762026-10-08redhat
redhatrhc-1:0.2.2-1.el9_2.62026-10-08redhat
redhatrhc-1:0.2.4-9.el9_4.22026-10-08redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel9:17913961652026-10-08redhat
gogoogle.golang.org/grpc @ 1.82.2 (fixes < 1.82.2)—ghsa
gogoogle.golang.org/grpc @ 1.83.2 (fixes >= 1.83.0, < 1.83.2)—ghsa
gogoogle.golang.org/grpc @ 1.84.0-dev.0.20260825144003-d5a41119e0e3 (fixes >= 1.84.0-dev, < 1.84.0-dev.0.20260825144003-d5a41119e0e3)—ghsa
gogoogle.golang.org/grpc @ 1.85.0-dev.0.20260825072537-93e31b48545e (fixes >= 1.85.0-dev, < 1.85.0-dev.0.20260825072537-93e31b48545e)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-google-grpc1.33.3-2 ... 1.81.1-1 (24 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-google-grpc1.64.0-7 ... 1.81.1-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-google-grpc1.64.0-7 ... 1.81.1-1 (7 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
google.golang.org/grpc—
  • every version up to 1.82.2: fixed in 1.82.2
  • 1.83.0 up to 1.83.2: fixed in 1.83.2
  • 1.84.0-dev up to 1.84.0-dev.0.20260825144003-d5a41119e0e3: fixed in 1.84.0-dev.0.20260825144003-d5a41119e0e3
  • 1.85.0-dev up to 1.85.0-dev.0.20260825072537-93e31b48545e: fixed in 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

(25)

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 11× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 137 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 37 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-2v4p-qf9q-27wj · GitHub severity HIGH
  3. 2026-11-01 07:38 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-10-27 21:17 UTCEG score recompute
  9. 2026-10-27 21:17 UTCVendor advisory
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  13. 2026-10-25 13:56 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  19. 2026-10-20 09:36 UTCEG score recompute
  20. 2026-10-20 09:36 UTCVendor advisory
  21. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  22. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  23. 2026-10-18 03:06 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 49th percentile
Show 75 more
  1. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-13 05:36 UTCEG score recompute
  5. 2026-10-13 05:36 UTCVendor advisory
  6. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  7. 2026-10-12 14:53 UTCEG score recompute
  8. 2026-10-11 22:53 UTCVendor advisory
  9. 2026-10-11 19:18 UTCEG score recompute
  10. 2026-10-11 16:35 UTCEG score recompute
  11. 2026-10-11 13:52 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-11 10:28 UTCEG score recompute
  14. 2026-10-11 10:28 UTCVendor advisory
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-10 08:32 UTCVendor advisory
  17. 2026-10-09 20:24 UTCEG score recompute
  18. 2026-10-09 20:24 UTCVendor advisory
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  20. 2026-10-09 00:24 UTCEG score recompute
  21. 2026-10-09 00:24 UTCVendor advisory
  22. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  23. 2026-10-08 02:37 UTCEG score recompute
  24. 2026-10-08 02:37 UTCVendor advisory
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  26. 2026-10-07 14:45 UTCVendor advisory
  27. 2026-10-07 02:06 UTCEG score recompute
  28. 2026-10-07 02:06 UTCVendor advisory
  29. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  30. 2026-10-06 14:11 UTCVendor advisory
  31. 2026-10-06 02:22 UTCEG score recompute
  32. 2026-10-06 02:22 UTCVendor advisory
  33. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  34. 2026-10-05 14:29 UTCVendor advisory
  35. 2026-10-05 02:38 UTCEG score recompute
  36. 2026-10-05 02:38 UTCVendor advisory
  37. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  38. 2026-10-04 14:49 UTCVendor advisory
  39. 2026-10-04 03:00 UTCVendor advisory
  40. 2026-10-03 15:10 UTCEG score recompute
  41. 2026-10-03 15:10 UTCVendor advisory
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  43. 2026-10-03 03:18 UTCEG score recompute
  44. 2026-10-03 03:18 UTCVendor advisory
  45. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  46. 2026-10-02 15:28 UTCVendor advisory
  47. 2026-10-02 03:31 UTCEG score recompute
  48. 2026-10-02 03:31 UTCVendor advisory
  49. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  50. 2026-10-01 14:39 UTCVendor advisory
  51. 2026-10-01 02:49 UTCEG score recompute
  52. 2026-10-01 02:49 UTCVendor advisory
  53. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  54. 2026-09-30 15:00 UTCVendor advisory
  55. 2026-09-30 02:12 UTCEG score recompute
  56. 2026-09-30 02:12 UTCVendor advisory
  57. 2026-09-29 14:12 UTCVendor advisory
  58. 2026-09-29 02:22 UTCEG score recompute
  59. 2026-09-29 02:22 UTCVendor advisory
  60. 2026-09-28 14:32 UTCEG score recompute
  61. 2026-09-28 14:32 UTCVendor advisory
  62. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  63. 2026-09-28 02:37 UTCVendor advisory
  64. 2026-09-27 14:47 UTCEG score recompute
  65. 2026-09-27 14:47 UTCVendor advisory
  66. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  67. 2026-09-27 02:58 UTCEG score recompute
  68. 2026-09-27 02:58 UTCVendor advisory
  69. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  70. 2026-09-26 15:08 UTCVendor advisory
  71. 2026-09-26 02:23 UTCEG score recompute
  72. 2026-09-26 02:23 UTCVendor advisory
  73. 2026-09-25 14:25 UTCVendor advisory
  74. 2026-09-25 07:08 UTCVendor advisory
  75. 2026-09-24 19:18 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-84445?
CVE-2026-84445 is a high-severity vulnerability; its CVE record was published on September 8, 2026. 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…
When was the CVE record for CVE-2026-84445 published?
The CVE record for CVE-2026-84445 was published on September 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-84445 actively exploited?
CVE-2026-84445 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84445?
CVE-2026-84445 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84445?
A fix for CVE-2026-84445 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84445 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84445

Explore →

Is Your Infrastructure Affected by CVE-2026-84445?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.