CVE-2026-109841: undici vulnerable to Subresource Integrity bypass via non-lowercase algorithm tokens
undici’s fetch() verifies Subresource Integrity (SRI) metadata by looking up the algorithm token in a lowercase-only set, but the SRI specification defines a valid token by its ASCII-lowercase form. A correct but non-lowercase token such as SHA256-... or Sha256-... is therefore treated as unknown and skipped. When no recognized algorithm remains, undici treats the integrity list as empty and accepts the response, so a server that returns a body different from the pinned digest passes the check.
An application that pins a response with a valid uppercase or mixed-case SRI token receives attacker-controlled bytes with no integrity error. The attacker needs only to control the response body, not the application’s integrity metadata. The issue affects response integrity only. The regression was introduced in undici 7.15.0; releases 7.14.0 and earlier lowercase the token and are not affected.
References
- cna.openjsf.org/security-advisories.html
- github.com/advisories/GHSA-f72v-6w45-q472
- github.com/nodejs/undici/commit/18bc8a1e09d15bc45815154a289dcf6fd5254d00
- github.com/nodejs/undici/commit/4f7ef6806e532ab9e29ccd6229b1b9d241e1b1f0
- github.com/nodejs/undici/releases/tag/v7.30.1
- github.com/nodejs/undici/releases/tag/v8.12.2
- github.com/nodejs/undici/security/advisories/GHSA-f72v-6w45-q472
- nvd.nist.gov/vuln/detail/CVE-2026-109841
Code Behaviors & Features
Detect and mitigate CVE-2026-109841 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →