Skip to content
Fencer Intel
medium 5.9

CVE-2026-109841 json

undici vulnerable to Subresource Integrity bypass via non-lowercase algorithm tokens

published 25d ago modified 17d ago also GHSA-f72v-6w45-q472 , EUVD-2026-102305

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

undici is an HTTP client library for Node.js. In versions 7.15.0 through 7.30.0 and 8.0.0 through 8.12.1, its fetch() implementation verifies Subresource Integrity metadata by matching the algorithm token against a lowercase-only set, even though the SRI specification defines the token by its ASCII-lowercase form, so a valid but non-lowercase token such as an uppercase or mixed-case SHA256 is treated as unknown and skipped. When no recognized algorithm remains, undici treats the integrity list as empty and accepts the response, so a server returning a body that does not match the pinned digest passes the check. An attacker who controls only the response body can therefore deliver attacker-controlled bytes to an application that pinned a valid uppercase or mixed-case SRI token, with no integrity error, affecting response integrity only. The issue is fixed in undici 7.30.1 and 8.12.2, which normalize the algorithm token to ASCII lowercase before validation, and users should upgrade to one of those versions or later. As a workaround, use lowercase algorithm tokens such as sha256, sha384, or sha512 in integrity metadata.

Patch / fix

  • npm undici 7.30.1, 8.12.2
  • undici undici 7.30.1, 8.12.2
  • node-undici Debian 14 8.12.2+dfsg+~cs3.2.3-1

debian advisories DEBIAN-CVE-2026-109841

  • nodejs24 hummingbird 1 24.21.0-1.5.hum1
  • nodejs24-bin hummingbird 1 24.21.0-1.5.hum1
  • nodejs24-npm hummingbird 1 11.19.0-1.24.21.0.1.5.hum1
  • nodejs24-libs hummingbird 1 24.21.0-1.5.hum1
  • nodejs24-npm-bin hummingbird 1 24.21.0-1.5.hum1
  • nodejs24-full-i18n hummingbird 1 24.21.0-1.5.hum1
  • nodejs26 hummingbird 1 26.11.1-0.4.hum1
  • nodejs26-bin hummingbird 1 26.11.1-0.4.hum1

red hat advisories RHSA-2026:84706RHSA-2026:84657

Is CVE-2026-109841 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-109841 updated cvss 5.9

undici: undici: Subresource Integrity bypass via non-lowercase algorithm tokens

  • Red Hat Cryostat 4 cryostat/cryostat-openshift-console-plugin-rhel9
    affected: no fix available “Fix deferred”
  • Red Hat Exploit Intelligence exploit-intelligence/vulnerability-analysis-rhel9
    affected: no fix planned “Out of support scope”
  • Red Hat AMQ Broker 7 amq-broker-bin.zip 7.14.1.CR3, amq-broker-maven-repository.zip 7.14.1.CR3 Red Hat Ansible Automation Platform 2 automation-platform-ui 2.6.15-1.el9ap Red Hat Build of Podman Desktop rh-podman-desktop a4ea1f988eb28bc86ab3516bba3a4973b252a17e
    affected: no fix available “Fix deferred”
  • Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9, rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend-module-loki, rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator
    affected: no fix available
  • Red Hat Enterprise Linux 8 npm, nodejs, nodejs-libs, ubi8/s2i-base, nodejs-nodemon, ubi8/nodejs-24, +4 more Red Hat Enterprise Linux 9 npm, nodejs, nodejs-libs, ubi9/nodejs-24, nodejs-full-i18n, ubi9/nodejs-24-minimal Red Hat Enterprise Linux 10 ubi10/nodejs-24, grafana 12.4.3-2.el10, nodejs26 26.1.0-1.el10, ubi10/nodejs-24-minimal, nodejs22 22.23.2-3.el10_2, nodejs24 24.21.0-1.el10_2
    affected: no fix available “Fix deferred”
  • Red Hat Hardened Images nodejs25 25.9.0-1.7.hum1
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-core-bff-rhel9, rhoai/odh-dashboard-rhel9, rhoai/odh-mod-arch-maas-rhel9, rhoai/odh-mod-arch-automl-rhel9, rhoai/odh-mod-arch-gen-ai-rhel9, +7 more Red Hat OpenShift Container Platform 4 wasmedge, wasmedge-rt, openshift4/ose-monitoring-plugin-rhel9 Red Hat OpenShift Container Platform 5 openshift5/ose-monitoring-plugin-rhel9 Red Hat Openshift Data Foundation 4 odf4/mcg-core-rhel9, odf4/odf-console-rhel9, odf4/ocs-client-console-rhel9, odf4/odf-multicluster-console-rhel9
    affected: no fix available “Fix deferred”
  • Red Hat OpenShift Dev Spaces devspaces/code-rhel9, devspaces/openvsx-rhel9, devspaces/dashboard-rhel9, devspaces/pluginregistry-rhel9
    affected: no fix available
show 5 more
  • Red Hat Secrets Management Console for Red Hat OpenShift external-secrets-management/console-plugin-rhel9
    affected: no fix planned “Out of support scope”
  • Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portal, ansible-automation-platform/bootc-automation-portal-rhel9
    affected: no fix available “Fix deferred”
  • Red Hat Hardened Images nodejs24 24.21.0-1.5.hum1, nodejs26 26.11.1-0.4.hum1, nodejs24-bin 24.21.0-1.5.hum1, nodejs26-bin 26.11.1-0.4.hum1, nodejs24-libs 24.21.0-1.5.hum1, nodejs26-libs 26.11.1-0.4.hum1, +6 more
    fixed: vendor fix RHSA-2026:84706
  • Red Hat Trusted Artifact Signer 1.5 rhtas/rhtas-console-ui-rhel9 1793114810
    fixed: vendor fix RHSA-2026:95124
  • Red Hat Hardened Images grafana12.4 12.4.12-0.4.hum1 Red Hat Trusted Artifact Signer 1.5 rhtas/rhtas-console-rhel9 1793108442
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
24d ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm undici
>=7.15.0, <7.30.1
>=8.0.0, <8.12.2
7.30.1
8.12.2

Affected products

  • undici undici

Classification

Weakness
  • CWE-178 Improper Handling of Case Sensitivity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.