{"items":[{"id":"NVI-00015253","kind":"vulnerability","title":"libp2p: yamux connection DoS via oversized data frame","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-hmj8-5xmh-5573","CVE-2026-73568"],"plain_summary":"GitHub lists this reviewed advisory for libp2p. 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-27f58b2686928e6e4c8f8e460c9d858f"],"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":"CVSS","as_of":"2026-08-13T17:43:44.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4a53c60fea4185f170dcbf2a62850ca5"},{"kind":"CVSS","as_of":"2026-10-24T15:10:00.190Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-27f58b2686928e6e4c8f8e460c9d858f"}],"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-4a53c60fea4185f170dcbf2a62850ca5","url":"https://github.com/advisories/GHSA-hmj8-5xmh-5573","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-hmj8-5xmh-5573","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T20:16:47.162Z"},{"id":"sr-27f58b2686928e6e4c8f8e460c9d858f","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-73568","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-73568","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T19:45:24.870Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4a53c60fea4185f170dcbf2a62850ca5"],"technology":"libp2p","known_exclusions":[],"conditions_summary":"### Summary\nThe yamux stream multiplexer in py-libp2p does not validate incoming DATA frame lengths against the receive window before reading the frame body. Any peer that completes a standard libp2p handshake can send a single 12-byte frame claiming a 4 GB body, causing the victim's yamux read loop to block indefinitely. This affects the default `new_host()` configuration and requires no special setup on either side.\n\n### Details\nIn `libp2p/stream_muxer/yamux/yamux.py` (lines 915 to 926), the `handle_incoming()` method dispatches on frame type. When a DATA frame arrives, it reads the body unconditionally:\n\n```python\nelif typ == TYPE_DATA:\n    try:\n        data = (\n            await read_exactly(self.secured_conn, length)\n            if length > 0\n            else b\"\"\n        )\n```\n\nThe `length` field is taken directly from the wire-decoded frame header, a 32-bit unsigned integer with a maximum value of 4,294,967,295. There is no check that `length` fits within the stream's receive window (`DEFAULT_WINDOW_SIZE = 256 * 1024` bytes). The body read also happens before the code checks whether the referenced `stream_id` even exists in `self.streams` (that check is at line 954), so any s","public_affected_ranges":["<= 0.7.0"]}],"null_published_at":"2026-11-08T19:53:44.042Z","source_updated_at":"2026-08-13T17:43:44.000Z","source_disclosed_at":"2026-07-24T22:37:17.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-02T20:16:47.162Z"},{"id":"NVI-00015253","kind":"vulnerability","title":"libp2p: yamux connection DoS via oversized data frame","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hmj8-5xmh-5573","CVE-2026-73568"],"plain_summary":"GitHub lists this reviewed advisory for libp2p. 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-4a53c60fea4185f170dcbf2a62850ca5"],"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":"CVSS","as_of":"2026-08-13T17:43:44.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4a53c60fea4185f170dcbf2a62850ca5"}],"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-4a53c60fea4185f170dcbf2a62850ca5","url":"https://github.com/advisories/GHSA-hmj8-5xmh-5573","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-hmj8-5xmh-5573","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T20:16:47.162Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4a53c60fea4185f170dcbf2a62850ca5"],"technology":"libp2p","known_exclusions":[],"conditions_summary":"### Summary\nThe yamux stream multiplexer in py-libp2p does not validate incoming DATA frame lengths against the receive window before reading the frame body. Any peer that completes a standard libp2p handshake can send a single 12-byte frame claiming a 4 GB body, causing the victim's yamux read loop to block indefinitely. This affects the default `new_host()` configuration and requires no special setup on either side.\n\n### Details\nIn `libp2p/stream_muxer/yamux/yamux.py` (lines 915 to 926), the `handle_incoming()` method dispatches on frame type. When a DATA frame arrives, it reads the body unconditionally:\n\n```python\nelif typ == TYPE_DATA:\n    try:\n        data = (\n            await read_exactly(self.secured_conn, length)\n            if length > 0\n            else b\"\"\n        )\n```\n\nThe `length` field is taken directly from the wire-decoded frame header, a 32-bit unsigned integer with a maximum value of 4,294,967,295. There is no check that `length` fits within the stream's receive window (`DEFAULT_WINDOW_SIZE = 256 * 1024` bytes). The body read also happens before the code checks whether the referenced `stream_id` even exists in `self.streams` (that check is at line 954), so any s","public_affected_ranges":["<= 0.7.0"]}],"null_published_at":"2026-11-03T10:03:26.565Z","source_updated_at":"2026-08-13T17:43:44.000Z","source_disclosed_at":"2026-07-24T22:37:17.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-02T20:16:47.162Z"}],"next_cursor":null,"snapshot_revision":"42594"}