Resource exhaustion in Grpc Grpc-Go
CVE-2026-84304
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.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
EPSS exploit prediction
EPSS: 0.006 (48.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 48th percentile — 48.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.006 · change: +0.002
Affected products
- Grpc Grpc-Go — versions < 1.83.1
Weakness classification (CWE)
References
- github.com/grpc/grpc-go/security/advisories/GHSA-vp52-pcj8-j9qc
- github.com/grpc/grpc-go/pull/9331
- github.com/grpc/grpc-go/pull/9333
- github.com/grpc/grpc-go/commit/7354d9c8debb4bcf2225bf429857078de310c176
- github.com/grpc/grpc-go/commit/8cfeca0e1ee5ea0980dcc320e20240fa1079ec77
- github.com/grpc/grpc-go/releases/tag/v1.83.1