CVE-2026-106074 Affecting nodejs24 package, versions <24.22.1-150700.15.21.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server 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-SLES157-NODEJS24-22192650
  • published4 Nov 2026
  • disclosed2 Nov 2026

Introduced: 2 Nov 2026

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

How to fix?

Upgrade SLES:15.7 nodejs24 to version 24.22.1-150700.15.21.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs24 package and not the nodejs24 package as distributed by SLES. See How to fix? for SLES:15.7 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