{"items":[{"id":"NVI-00010604","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unbounded memory in the EventSource parser","revision":5,"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-4qv8-2p9j-2685","CVE-2026-109924"],"plain_summary":"GitHub lists this reviewed advisory for undici, undici, undici. 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-2cc1d4cc5a5b0a7e21417169bf861d3f"],"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},{"summary":"The original advisory lists fixed boundaries 6.29.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.30.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.12.2 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"action_type":"vendor_patch","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-10-23T22:13:31.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6789097edf7aeaabd717324a838abca1"},{"kind":"CVSS","as_of":"2026-10-19T20:45:00.433Z","value":"5.9 MEDIUM (3.1)","meaning":"ce714d77-add3-4f53-aff5-83d477b104bb severity; no combined Null risk score.","source_id":"sr-2910d2a525d491dd651484427f80f27b"},{"kind":"CVSS","as_of":"2026-10-19T20:45:00.433Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2910d2a525d491dd651484427f80f27b"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.321%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.25125. Missing scores are unknown.","source_id":"sr-2cc1d4cc5a5b0a7e21417169bf861d3f"}],"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-6789097edf7aeaabd717324a838abca1","url":"https://github.com/advisories/GHSA-4qv8-2p9j-2685","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4qv8-2p9j-2685","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-8359de8d4633610f1ef7924f94ae3f6f","url":"https://github.com/advisories/GHSA-4qv8-2p9j-2685","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4qv8-2p9j-2685","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-04T02:47:41.615Z"},{"id":"sr-2910d2a525d491dd651484427f80f27b","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-109924","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-109924","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:37.778Z"},{"id":"sr-2cc1d4cc5a5b0a7e21417169bf861d3f","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-109924","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.265Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 6.5.0, < 6.29.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 7.0.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 8.0.0, < 8.12.2"]},{"certainty":"source_listed","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":["SEMVER: introduced 6.5.0; fixed 6.29.1"]},{"certainty":"source_listed","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":["SEMVER: introduced 7.0.0; fixed 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.12.2"]}],"null_published_at":"2026-11-06T15:18:11.461Z","source_updated_at":"2026-10-23T22:13:31.000Z","source_disclosed_at":"2026-10-23T22:13:29.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-10-31T22:07:08.657Z"},{"id":"NVI-00010604","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unbounded memory in the EventSource parser","revision":4,"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-4qv8-2p9j-2685","CVE-2026-109924"],"plain_summary":"GitHub lists this reviewed advisory for undici, undici, undici. 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-673f6a1c254165e75426773ce3e691a1"],"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},{"summary":"The original advisory lists fixed boundaries 6.29.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.30.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.12.2 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"action_type":"vendor_patch","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-10-23T22:13:31.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6789097edf7aeaabd717324a838abca1"},{"kind":"CVSS","as_of":"2026-10-19T20:45:00.433Z","value":"5.9 MEDIUM (3.1)","meaning":"ce714d77-add3-4f53-aff5-83d477b104bb severity; no combined Null risk score.","source_id":"sr-2910d2a525d491dd651484427f80f27b"},{"kind":"CVSS","as_of":"2026-10-19T20:45:00.433Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2910d2a525d491dd651484427f80f27b"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.321%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.2513. Missing scores are unknown.","source_id":"sr-673f6a1c254165e75426773ce3e691a1"}],"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-6789097edf7aeaabd717324a838abca1","url":"https://github.com/advisories/GHSA-4qv8-2p9j-2685","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4qv8-2p9j-2685","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-8359de8d4633610f1ef7924f94ae3f6f","url":"https://github.com/advisories/GHSA-4qv8-2p9j-2685","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4qv8-2p9j-2685","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-04T02:47:41.615Z"},{"id":"sr-2910d2a525d491dd651484427f80f27b","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-109924","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-109924","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:37.778Z"},{"id":"sr-673f6a1c254165e75426773ce3e691a1","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-109924","publisher":"FIRST EPSS","observed_at":"2026-10-31T23:13:27.688Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 6.5.0, < 6.29.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 7.0.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 8.0.0, < 8.12.2"]},{"certainty":"source_listed","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":["SEMVER: introduced 6.5.0; fixed 6.29.1"]},{"certainty":"source_listed","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":["SEMVER: introduced 7.0.0; fixed 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-8359de8d4633610f1ef7924f94ae3f6f"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.12.2"]}],"null_published_at":"2026-11-05T03:52:54.737Z","source_updated_at":"2026-10-23T22:13:31.000Z","source_disclosed_at":"2026-10-23T22:13:29.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-10-31T22:07:08.657Z"},{"id":"NVI-00010604","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unbounded memory in the EventSource parser","revision":3,"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-4qv8-2p9j-2685","CVE-2026-109924"],"plain_summary":"GitHub lists this reviewed advisory for undici, undici, undici. 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-673f6a1c254165e75426773ce3e691a1"],"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-10-23T22:13:31.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6789097edf7aeaabd717324a838abca1"},{"kind":"CVSS","as_of":"2026-10-19T20:45:00.433Z","value":"5.9 MEDIUM (3.1)","meaning":"ce714d77-add3-4f53-aff5-83d477b104bb severity; no combined Null risk score.","source_id":"sr-2910d2a525d491dd651484427f80f27b"},{"kind":"CVSS","as_of":"2026-10-19T20:45:00.433Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2910d2a525d491dd651484427f80f27b"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.321%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.2513. Missing scores are unknown.","source_id":"sr-673f6a1c254165e75426773ce3e691a1"}],"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-6789097edf7aeaabd717324a838abca1","url":"https://github.com/advisories/GHSA-4qv8-2p9j-2685","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4qv8-2p9j-2685","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-2910d2a525d491dd651484427f80f27b","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-109924","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-109924","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:37.778Z"},{"id":"sr-673f6a1c254165e75426773ce3e691a1","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-109924","publisher":"FIRST EPSS","observed_at":"2026-10-31T23:13:27.688Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 6.5.0, < 6.29.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 7.0.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 8.0.0, < 8.12.2"]}],"null_published_at":"2026-11-03T10:03:31.385Z","source_updated_at":"2026-10-23T22:13:31.000Z","source_disclosed_at":"2026-10-23T22:13:29.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-10-31T22:07:08.657Z"},{"id":"NVI-00010604","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unbounded memory in the EventSource parser","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4qv8-2p9j-2685","CVE-2026-109924"],"plain_summary":"GitHub lists this reviewed advisory for undici, undici, undici. 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-673f6a1c254165e75426773ce3e691a1"],"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-10-23T22:13:31.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6789097edf7aeaabd717324a838abca1"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.321%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.2513. Missing scores are unknown.","source_id":"sr-673f6a1c254165e75426773ce3e691a1"}],"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-6789097edf7aeaabd717324a838abca1","url":"https://github.com/advisories/GHSA-4qv8-2p9j-2685","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4qv8-2p9j-2685","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-673f6a1c254165e75426773ce3e691a1","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-109924","publisher":"FIRST EPSS","observed_at":"2026-10-31T23:13:27.688Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 6.5.0, < 6.29.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 7.0.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 8.0.0, < 8.12.2"]}],"null_published_at":"2026-11-01T22:58:19.138Z","source_updated_at":"2026-10-23T22:13:31.000Z","source_disclosed_at":"2026-10-23T22:13:29.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-10-31T22:07:08.657Z"},{"id":"NVI-00010604","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unbounded memory in the EventSource parser","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4qv8-2p9j-2685","CVE-2026-109924"],"plain_summary":"GitHub lists this reviewed advisory for undici, undici, undici. 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-6789097edf7aeaabd717324a838abca1"],"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-10-23T22:13:31.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-6789097edf7aeaabd717324a838abca1"}],"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-6789097edf7aeaabd717324a838abca1","url":"https://github.com/advisories/GHSA-4qv8-2p9j-2685","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4qv8-2p9j-2685","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 6.5.0, < 6.29.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 7.0.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-6789097edf7aeaabd717324a838abca1"],"technology":"undici","known_exclusions":[],"conditions_summary":"### Impact\n\nundici's `EventSource` client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed `data:` fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state. The byte-based `maxEventSize` and `maxResponseSize` limits do not bound that retained state, and `maxResponseSize` is enforced on the compressed body before decompression, so a small compressed response can expand into enough retained memory to terminate the process. The application only needs to maintain an `EventSource` connection to an untrusted peer, which controls only the response. Availability is the only impact.\n\n### Patches\n\nUpgrade to `6.29.1`, `7.30.1`, or `8.12.2`, which bound the retained EventSource parser state (the number of `data` fields and buffered chunks, the unfinished-line length, and per-field byte totals) independently of the byte limits.\n\n### Workarounds\n\nNone.","public_affected_ranges":[">= 8.0.0, < 8.12.2"]}],"null_published_at":"2026-10-31T22:27:09.625Z","source_updated_at":"2026-10-23T22:13:31.000Z","source_disclosed_at":"2026-10-23T22:13:29.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-10-31T22:07:08.657Z"}],"next_cursor":null,"snapshot_revision":"42594"}