Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation in google.golang.org/grpc
Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation in google.golang.org/grpc
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-84304US | — | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/grpc/grpc-go/commit/7354d9c8debb4bcf2225bf429857078de310c176FIX
- https://github.com/grpc/grpc-go/commit/8cfeca0e1ee5ea0980dcc320e20240fa1079ec77WEB
- https://github.com/grpc/grpc-go/pull/9331WEB
- https://github.com/grpc/grpc-go/pull/9333WEB
- https://github.com/grpc/grpc-go/releases/tag/v1.83.1WEB
- https://github.com/grpc/grpc-go/security/advisories/GHSA-vp52-pcj8-j9qcADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan