# CVE-2026-120423: undici vulnerable to Subresource Integrity bypass via whitespace in integrity metadata


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 6 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** AZL-113233, DEBIAN-CVE-2026-120423, GHSA-r4pc-4jcp-7pqc, UBUNTU-CVE-2026-120423

## What is CVE-2026-120423?

CVE-2026-120423 is a medium-severity vulnerability in undici, published on 6 Nov 2026. 

### Official description

undici 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.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2026-120423?


## How do I fix CVE-2026-120423?

Upgrade to a fixed version.

## Is CVE-2026-120423 being exploited?

There is no known exploitation of CVE-2026-120423 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120423 and fix it if it is affected.

What it is: CVE-2026-120423 is a medium-severity vulnerability in undici, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120423 in the wild and no public exploit code.

Affected product: undici. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120423/ (Markdown: https://insights.sbomify.com/CVE-2026-120423/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120423
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120423
- OSV: https://osv.dev/vulnerability/CVE-2026-120423

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120423/
Summaries are generated and may contain mistakes; the official description above is the record.
