CVE-2026-106074 Affecting nodejs:24/npm package, versions <1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1


Severity

Recommended
high

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.33% (27th 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-ALMALINUX8-NODEJS-21872731
  • published30 Oct 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-106074  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 nodejs:24/npm to version 1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 or higher.
This issue was patched in ALSA-2026:92376.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:24/npm package and not the nodejs:24/npm package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

A flaw in Node.js crypto causes the internal entropy caches used by crypto.randomUUID(), crypto.randomUUIDv7(), and crypto.randomInt() to be saved into user-land startup snapshots (--build-snapshot) and single executable applications built with useSnapshot.

If any of these functions, or an API that relies on them such as URL.createObjectURL(), is called while the snapshot is built, every process started from that snapshot returns the same values until the cache is refilled: up to 127 UUIDs and about 1,000 randomInt() values. Identifiers expected to be unique can collide across processes, and values issued by one process can be predicted by observing another.

This vulnerability affects Node.js 26.x, 24.x, and 22.x.

CVSS Base Scores

version 3.1