Improper Validation of Integrity Check Value Affecting nodejs24-libs package, versions <1:24.22.1-1.amzn2023.0.1


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.25% (17th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-NODEJS24LIBS-21707080
  • published25 Oct 2026
  • disclosed15 Oct 2026

Introduced: 15 Oct 2026

NewCVE-2026-109841  (opens in a new tab)
CWE-354  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 nodejs24-libs to version 1:24.22.1-1.amzn2023.0.1 or higher.
This issue was patched in ALAS2023-2026-3330.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs24-libs package and not the nodejs24-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1