Menu

Node.js randomInt cache persistence in snapshots: scope and limits
📰

Node.js randomInt cache persistence in snapshots: scope and limits

DEV Community: node·Ioneyrezende·15 days ago
#xOX8FLEr
#devtonodejs#devto#dev#node#snapshot
Reading 0:00
15s threshold

Node.js randomInt cache persistence in snapshots: scope and limits

Overview

Node.js has fixed a medium-severity issue in which cached crypto entropy can become part of user-land startup snapshots and single executable applications. CVE-2026-106074 affects the 22.x, 24.x, and 26.x lines and is fixed in 22.23.4, 24.22.1, and 26.12.1.

The named functions are crypto.randomUUID() , crypto.randomUUIDv7() , and crypto.randomInt() . The bug does not mean these APIs always return predictable values. It means a specific snapshot build path can preserve cached values for later processes.

What the snapshot stores

A user-land snapshot can retain initialized JavaScript state. The vulnerable runtime includes entropy used by the affected crypto functions in that state. A single executable application built with useSnapshot then packages the snapshot for repeated launches.

Calling a random API during the build is the trigger described by Node.js.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.