{"items":[{"id":"NVI-00008856","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor","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-55wc-3pg8-jfw6","CVE-2026-87029"],"plain_summary":"GitHub lists this reviewed advisory for 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-16537d7f863905d0e57765c6d76ead15"],"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 7.30.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"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-d7ac7eb1304f3fd622760f6afd327118"],"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-27T19:02:12.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0781f898e2da095a2ada35f86892d66b"},{"kind":"CVSS","as_of":"2026-10-19T20:41:00.667Z","value":"5.9 MEDIUM (3.1)","meaning":"ce714d77-add3-4f53-aff5-83d477b104bb severity; no combined Null risk score.","source_id":"sr-30ea869bb785b35ece7b173f12fd35d4"},{"kind":"CVSS","as_of":"2026-10-19T20:41:00.667Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-30ea869bb785b35ece7b173f12fd35d4"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.260%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.17872. Missing scores are unknown.","source_id":"sr-16537d7f863905d0e57765c6d76ead15"}],"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-0781f898e2da095a2ada35f86892d66b","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-d7ac7eb1304f3fd622760f6afd327118","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-02T02:21:57.254Z"},{"id":"sr-30ea869bb785b35ece7b173f12fd35d4","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87029","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-87029","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:30.678Z"},{"id":"sr-16537d7f863905d0e57765c6d76ead15","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-87029","publisher":"FIRST EPSS","observed_at":"2026-11-04T23:33:33.076Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 7.15.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 8.0.0, < 8.12.2"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 7.15.0; fixed 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.12.2"]}],"null_published_at":"2026-11-08T19:53:38.932Z","source_updated_at":"2026-10-27T19:02:12.000Z","source_disclosed_at":"2026-10-27T19:02:10.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-31T21:56:36.327Z"},{"id":"NVI-00008856","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor","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-55wc-3pg8-jfw6","CVE-2026-87029"],"plain_summary":"GitHub lists this reviewed advisory for 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-b6980baa76ec602622ff9b2f1127270a"],"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 7.30.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"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-d7ac7eb1304f3fd622760f6afd327118"],"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-27T19:02:12.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0781f898e2da095a2ada35f86892d66b"},{"kind":"CVSS","as_of":"2026-10-19T20:41:00.667Z","value":"5.9 MEDIUM (3.1)","meaning":"ce714d77-add3-4f53-aff5-83d477b104bb severity; no combined Null risk score.","source_id":"sr-30ea869bb785b35ece7b173f12fd35d4"},{"kind":"CVSS","as_of":"2026-10-19T20:41:00.667Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-30ea869bb785b35ece7b173f12fd35d4"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.260%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.17806. Missing scores are unknown.","source_id":"sr-b6980baa76ec602622ff9b2f1127270a"}],"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-0781f898e2da095a2ada35f86892d66b","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-d7ac7eb1304f3fd622760f6afd327118","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-02T02:21:57.254Z"},{"id":"sr-30ea869bb785b35ece7b173f12fd35d4","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87029","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-87029","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:30.678Z"},{"id":"sr-b6980baa76ec602622ff9b2f1127270a","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-87029","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.385Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 7.15.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 8.0.0, < 8.12.2"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 7.15.0; fixed 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.12.2"]}],"null_published_at":"2026-11-05T03:52:54.815Z","source_updated_at":"2026-10-27T19:02:12.000Z","source_disclosed_at":"2026-10-27T19:02:10.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-31T21:56:36.327Z"},{"id":"NVI-00008856","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor","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-55wc-3pg8-jfw6","CVE-2026-87029"],"plain_summary":"GitHub lists this reviewed advisory for 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-30ea869bb785b35ece7b173f12fd35d4"],"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 7.30.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"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-d7ac7eb1304f3fd622760f6afd327118"],"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-27T19:02:12.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0781f898e2da095a2ada35f86892d66b"},{"kind":"CVSS","as_of":"2026-10-19T20:41:00.667Z","value":"5.9 MEDIUM (3.1)","meaning":"ce714d77-add3-4f53-aff5-83d477b104bb severity; no combined Null risk score.","source_id":"sr-30ea869bb785b35ece7b173f12fd35d4"},{"kind":"CVSS","as_of":"2026-10-19T20:41:00.667Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-30ea869bb785b35ece7b173f12fd35d4"}],"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-0781f898e2da095a2ada35f86892d66b","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-d7ac7eb1304f3fd622760f6afd327118","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-02T02:21:57.254Z"},{"id":"sr-30ea869bb785b35ece7b173f12fd35d4","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87029","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-87029","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:30.678Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 7.15.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 8.0.0, < 8.12.2"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 7.15.0; fixed 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.12.2"]}],"null_published_at":"2026-11-04T10:04:35.927Z","source_updated_at":"2026-10-27T19:02:12.000Z","source_disclosed_at":"2026-10-27T19:02:10.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-31T21:56:36.327Z"},{"id":"NVI-00008856","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-55wc-3pg8-jfw6","CVE-2026-87029"],"plain_summary":"GitHub lists this reviewed advisory for 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-0781f898e2da095a2ada35f86892d66b"],"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 7.30.1 for undici. Confirm the publisher’s latest guidance.","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"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-d7ac7eb1304f3fd622760f6afd327118"],"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-27T19:02:12.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0781f898e2da095a2ada35f86892d66b"}],"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-0781f898e2da095a2ada35f86892d66b","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-d7ac7eb1304f3fd622760f6afd327118","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-02T02:21:57.254Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 7.15.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 8.0.0, < 8.12.2"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 7.15.0; fixed 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-d7ac7eb1304f3fd622760f6afd327118"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.12.2"]}],"null_published_at":"2026-11-02T20:21:10.349Z","source_updated_at":"2026-10-27T19:02:12.000Z","source_disclosed_at":"2026-10-27T19:02:10.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-31T21:56:36.327Z"},{"id":"NVI-00008856","kind":"vulnerability","title":"undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-55wc-3pg8-jfw6","CVE-2026-87029"],"plain_summary":"GitHub lists this reviewed advisory for 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-0781f898e2da095a2ada35f86892d66b"],"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-27T19:02:12.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0781f898e2da095a2ada35f86892d66b"}],"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-0781f898e2da095a2ada35f86892d66b","url":"https://github.com/advisories/GHSA-55wc-3pg8-jfw6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-55wc-3pg8-jfw6","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 7.15.0, < 7.30.1"]},{"certainty":"source_listed","source_ids":["sr-0781f898e2da095a2ada35f86892d66b"],"technology":"undici","known_exclusions":[],"conditions_summary":"## Impact\n\nundici's `decompress` interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw. undici's engine converts a synchronous throw from a downstream handler into a per-request failure, but that protection is not in place when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, for example the built-in `dump` interceptor which throws when a response exceeds its `maxSize`, escapes as an uncaught exception and terminates the Node.js process.\n\nA malicious or compromised HTTP server can crash any client that composes the `decompress` interceptor with `dump` (or another response handler that throws), by returning a small compressed body that decompresses to more than the configured limit. The compressed bytes on the wire are tiny, so only the decompressed size matters. If the application keeps the process alive with a global uncaught-exception handler, the affected request instead hangs until the body timeout.\n\n## Patches\n\nUpgrade to undici 7.30.1 or 8.12.2.\n\n## Workarounds\n\nAvoid composing the `decompress` interceptor wi","public_affected_ranges":[">= 8.0.0, < 8.12.2"]}],"null_published_at":"2026-10-31T22:13:27.119Z","source_updated_at":"2026-10-27T19:02:12.000Z","source_disclosed_at":"2026-10-27T19:02:10.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-31T21:56:36.327Z"}],"next_cursor":null,"snapshot_revision":"42594"}