{"items":[{"id":"NVI-00014031","kind":"vulnerability","title":"gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-vp52-pcj8-j9qc","CVE-2026-84304"],"plain_summary":"GitHub lists this reviewed advisory for google.golang.org/grpc. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1549ecf95b99ea64fdf59360374f657c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.609%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.49268. Missing scores are unknown.","source_id":"sr-1549ecf95b99ea64fdf59360374f657c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-34baa1b22533c7401fdc9beeb498baff","url":"https://github.com/advisories/GHSA-vp52-pcj8-j9qc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-vp52-pcj8-j9qc","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"},{"id":"sr-1549ecf95b99ea64fdf59360374f657c","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-84304","publisher":"FIRST EPSS","observed_at":"2026-11-04T23:33:33.072Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-34baa1b22533c7401fdc9beeb498baff"],"technology":"google.golang.org/grpc","known_exclusions":[],"conditions_summary":"### Impact\nAn 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.\n\nRepeated 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).\n\n### Patches\nThe change to fix this issue is merged in `master` and a patch release, 1.83.1, has been published that contains this fix.\n\n### Workarounds\nThis 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 perceived to be excessive relative to actual payload data, drastically minimizing per-frame memory overheads.\n\nThis behavior is enabled by default. A temporary escape hatch is provided via the","public_affected_ranges":["<= 1.83.0"]}],"null_published_at":"2026-11-08T19:53:38.928Z","source_updated_at":"2026-09-01T21:32:45.000Z","source_disclosed_at":"2026-09-01T21:32:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-02T02:21:50.763Z"},{"id":"NVI-00014031","kind":"vulnerability","title":"gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-vp52-pcj8-j9qc","CVE-2026-84304"],"plain_summary":"GitHub lists this reviewed advisory for google.golang.org/grpc. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-34baa1b22533c7401fdc9beeb498baff"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-34baa1b22533c7401fdc9beeb498baff","url":"https://github.com/advisories/GHSA-vp52-pcj8-j9qc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-vp52-pcj8-j9qc","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-34baa1b22533c7401fdc9beeb498baff"],"technology":"google.golang.org/grpc","known_exclusions":[],"conditions_summary":"### Impact\nAn 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.\n\nRepeated 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).\n\n### Patches\nThe change to fix this issue is merged in `master` and a patch release, 1.83.1, has been published that contains this fix.\n\n### Workarounds\nThis 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 perceived to be excessive relative to actual payload data, drastically minimizing per-frame memory overheads.\n\nThis behavior is enabled by default. A temporary escape hatch is provided via the","public_affected_ranges":["<= 1.83.0"]}],"null_published_at":"2026-11-02T10:00:37.198Z","source_updated_at":"2026-09-01T21:32:45.000Z","source_disclosed_at":"2026-09-01T21:32:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T02:21:50.763Z"}],"next_cursor":null,"snapshot_revision":"44495"}