Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://github.com/grpc/grpc-go/commit/7354d9c8debb4bcf2225bf429857078de310c176
- https://github.com/grpc/grpc-go/commit/8cfeca0e1ee5ea0980dcc320e20240fa1079ec77
- https://github.com/grpc/grpc-go/pull/9331
- https://github.com/grpc/grpc-go/pull/9333
- https://github.com/grpc/grpc-go/releases/tag/v1.83.1
- https://github.com/grpc/grpc-go/security/advisories/GHSA-vp52-pcj8-j9qc
FAQ
What is CVE-2026-84304?
CVE-2026-84304 is a documented vulnerability. 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-byt...
How severe is CVE-2026-84304?
CVSS scoring is not yet available for CVE-2026-84304. Check NVD for updates.
Is there a patch for CVE-2026-84304?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.