CVE-2026-120423 · Package
NO FIX YET · SEE WHAT TO DO
undici's fetch splits Subresource Integrity metadata only on a single space, so a digest preceded by a tab or other whitespace is ignored and the check passes. An attacker who controls the response body can therefore deliver bytes that differ from the pinned digest without an integrity error.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications using undici's fetch with Subresource Integrity values to pin response bodies are exposed when the integrity string has whitespace around the digest, such as a leading tab. Applications that do not use the integrity option, or that pin with clean single-space metadata, are not affected by this flaw.
Not affected if clean-sri-metadata, no-integrity-option
Who cares fetch, node.js, undici
npm ls undici to find installed undici versions in the project tree.fetch that pass an integrity option with a value containing tabs or other leading or trailing whitespace.7.30.28.12.4undici is an HTTP client for Node.js. In versions 7.15.0 through 7.30.1 and 8.0.0 through 8.12.3, fetch verifies Subresource Integrity metadata by splitting the integrity string on a single space, but the SRI grammar separates metadata by ASCII whitespace, which also includes the horizontal tab. An integrity value whose digest is preceded by a tab or other ASCII whitespace is parsed as a single unrecognized token and skipped, and when no recognized algorithm remains undici treats the integrity list as empty and accepts the response, so a server returning a body different from the pinned digest passes the check. An application that pins a response with a valid but whitespace-surrounded SRI value receives attacker-controlled bytes with no integrity error, and the attacker needs only to control the response body, not the integrity metadata. 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, supply SRI integrity metadata without surrounding whitespace, using a single space to separate multiple digests.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.