Bug 2579553 - CVE-2026-120222 nodejs24: undici: Denial of Service via uncaught exception during cached response replay [fedora-all]
Summary: CVE-2026-120222 nodejs24: undici: Denial of Service via uncaught exception du...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: nodejs24
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Jan Staněk
QA Contact:
URL:
Whiteboard: {"flaws": ["a5fdafc3-3331-4626-bb46-7...
Depends On:
Blocks: CVE-2026-120222
TreeView+ depends on / blocked
 
Reported: 2026-11-20 17:56 UTC by Avinash Hanwate
Modified: 2026-11-20 17:56 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Avinash Hanwate 2026-11-20 17:56:27 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when the cache interceptor is composed with a downstream handler that throws during response processing (such as the built-in dump interceptor exceeding its maxSize, or the decompress interceptor rejecting more than five Content-Encoding values), a throw raised asynchronously while a cached response is replayed escapes as an uncaught exception or unhandled promise rejection and terminates the Node.js process. A malicious or compromised HTTP server can crash any such client by serving a cacheable response that triggers the throw on replay, including on a 304 revalidation of a stale entry, so the impact is availability only. The issue is fixed in undici 7.30.2 and 8.12.4, and users should upgrade to one of those versions or later. As a workaround, avoid composing the cache interceptor with a response handler that throws during response processing until upgrading.


Note You need to log in before you can comment on or make changes to this bug.