CVE-2026-84304

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, internal/transport/transport.go stores each fragmented HTTP/2 DATA frame as a separate recvMsg in recvBuffer, so millions of one-byte frames can consume disproportionate heap memory even when payload bytes remain within connection and stream flow-control windows. An unauthenticated remote attacker can use concurrent multiplexed streams to exhaust process memory and cause a runtime panic or out-of-memory termination. Receive-buffer compaction is enabled by default and can be controlled temporarily with GRPC_GO_EXPERIMENTAL_ENABLE_RECEIVE_BUFFER_COMPACTION. This issue is fixed in version 1.83.1.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/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 computed
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 9, 2026

Advisory Details (6)

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

Release 1.83.1

Patch available: grpc/grpc-go v1.83.1

https://github.com/grpc/grpc-go/releases/tag/v1.83.1
github_commit Patch Available

commit 8cfeca0e1ee5 (grpc/grpc-go)

Patch available: grpc/grpc-go v1.83.1 (contains commit 8cfeca0e1ee5)

https://github.com/grpc/grpc-go/commit/8cfeca0e1ee5ea0980dcc320e20240fa1079ec77
github_commit

commit 7354d9c8debb (grpc/grpc-go)

Fix landed in grpc/grpc-go commit 7354d9c8debb — awaiting tagged release

https://github.com/grpc/grpc-go/commit/7354d9c8debb4bcf2225bf429857078de310c176
github_pr Patch Available

Cherry-pick #9331 to v1.83.x

Patch available: grpc/grpc-go v1.83.1 (PR #9333 merged 2026-08-19)

https://github.com/grpc/grpc-go/pull/9333
github_pr

transport: restrict memory overhead of buffering small data frames

Fix merged in grpc/grpc-go PR #9331 on 2026-08-19 — awaiting tagged release

https://github.com/grpc/grpc-go/pull/9331
github Patch Available

Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation in gRPC-Go · Advisory · grpc/grpc-go · GitHub

https://github.com/grpc/grpc-go/security/advisories/GHSA-vp52-pcj8-j9qc

Vendor Advisories for CVE-2026-84304(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-google-grpc1.33.3-2 ... 1.81.1-1 (24 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-google-grpc1.64.0-7 ... 1.81.1-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-google-grpc1.64.0-7 ... 1.81.1-1 (7 versions)——
Go(1)
PackageVulnerable rangeFixed inDependents
google.golang.org/grpc—1.83.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 56× 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.

  1. 2026-09-19 09:57 UTCVendor advisory
  2. 2026-09-18 21:25 UTCEG score recompute
  3. 2026-09-18 21:25 UTCVendor advisory
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 09:09 UTCVendor advisory
  6. 2026-09-17 21:13 UTCEG score recompute
  7. 2026-09-17 21:13 UTCVendor advisory
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 09:18 UTCVendor advisory
  10. 2026-09-16 21:22 UTCEG score recompute
  11. 2026-09-16 21:22 UTCVendor advisory
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 09:06 UTCEG score recompute
  14. 2026-09-16 09:06 UTCVendor advisory
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 20:54 UTCVendor advisory
  17. 2026-09-15 08:27 UTCEG score recompute
  18. 2026-09-15 08:27 UTCVendor advisory
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 20:30 UTCVendor advisory
  22. 2026-09-14 08:34 UTCVendor advisory
  23. 2026-09-13 20:38 UTCEG score recompute
  24. 2026-09-13 20:38 UTCVendor advisory
  25. 2026-09-13 08:42 UTCVendor advisory
Show 31 more
  1. 2026-09-12 20:47 UTCEG score recompute
  2. 2026-09-12 20:47 UTCVendor advisory
  3. 2026-09-12 08:51 UTCVendor advisory
  4. 2026-09-11 20:55 UTCEG score recompute
  5. 2026-09-11 20:55 UTCVendor advisory
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 21:03 UTCEG score recompute
  9. 2026-09-09 21:11 UTCVendor advisory
  10. 2026-09-09 11:18 UTCVendor advisory
  11. 2026-09-08 23:22 UTCEG score recompute
  12. 2026-09-08 23:22 UTCVendor advisory
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-08 07:44 UTCVendor advisory
  15. 2026-09-07 19:48 UTCEG score recompute
  16. 2026-09-07 19:48 UTCVendor advisory
  17. 2026-09-07 07:53 UTCVendor advisory
  18. 2026-09-06 19:53 UTCEG score recompute
  19. 2026-09-06 19:53 UTCVendor advisory
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-05 20:00 UTCEG score recompute
  22. 2026-09-05 15:31 UTCEPSS rescore
  23. 2026-09-04 20:08 UTCEG score recompute
  24. 2026-09-04 08:10 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
  26. 2026-09-02 20:19 UTCEG score recompute
  27. 2026-09-02 14:12 UTCEPSS rescore
  28. 2026-09-01 20:20 UTCEG score recompute
  29. 2026-09-01 19:29 UTCEG score recompute
  30. 2026-09-01 18:39 UTCEG score recompute
  31. 2026-09-01 18:37 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-84304?
CVE-2026-84304 is a high vulnerability published on September 1, 2026. gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, internal/transport/transport.go stores each fragmented HTTP/2 DATA frame as a separate recvMsg in recvBuffer, so millions of one-byte frames can consume disproportionate heap memory even when payload bytes remain within connection…
When was CVE-2026-84304 disclosed?
CVE-2026-84304 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84304 actively exploited?
CVE-2026-84304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.6% of all scored CVEs.
What is the CVSS score of CVE-2026-84304?
CVE-2026-84304 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-84304?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84304, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-84304?

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

Start Free Scan →Browse All CVEs