Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation

CVE-2026-84304GHSA-vp52-pcj8-j9qc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (google.golang.org/grpc 1.83.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-84304: 0.61% estimated exploitation activity in the next 30 days; percentile 49.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact An unauthenticated remote attacker can initiate a gRPC stream and purposefully fragment their payload into millions of tiny (e.g., 1-byte) HTTP/2 DATA frames. Even if the total payload volume falls within the configured connection and stream flow-control windows, each independent fragment incurs memory overhead due to internal tracking structures and queue allocation. Repeated fragmentation massively inflates the heap space consumed by the stream. An attacker multiplexing multiple concurrent streams can exhaust the memory bounds of the runtime, forcing a runtime panic or OutOfMemory condition and leading to a remote Denial of Service (DoS). Patches The change to fix this issue is merged in master and a patch release, 1.83.1, has been published that contains this fix. Workarounds This vulnerability is mitigated by implementing receive buffer compaction. Consecutive small data buffers are automatically coalesced into larger buffers from a shared pool once the overhead is…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-vp52-pcj8-j9qc

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6348

  4. Revision 1 · created ·

    Published from osv record GHSA-vp52-pcj8-j9qc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-84304

Advisory: gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation
IDs: CVE-2026-84304, GHSA-vp52-pcj8-j9qc
Record: https://patchnext.com/advisories/cve-2026-84304 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: google.golang.org/grpc 1.83.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go google.golang.org/grpc: affected <= 1.83.0; fixed in 1.83.1

## Suggested inspection (read-only)
- Go google.golang.org/grpc: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on google.golang.org/grpc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vp52-pcj8-j9qc (OSV record GHSA-vp52-pcj8-j9qc lists affected ranges: Go google.golang.org/grpc >=0 <1.83.1 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6348 (OSV record GO-2026-6348 lists affected ranges: Go google.golang.org/grpc >=0 <1.83.1 (fixed))
- Verified: https://github.com/advisories/GHSA-vp52-pcj8-j9qc (GitHub-reviewed advisory GHSA-vp52-pcj8-j9qc lists affected ranges: Go google.golang.org/grpc >=0 <=1.83.0)

Commands are suggestions: review each one before running it.

Loading voting…