Node.js CVE-2026-106074

Exploitation requires the target to be a Node.js application built or run using the startup snapshot feature (for example --build-snapshot / --snapshot-blob, or single-executable applications), where the crypto random cache was captured in the snapshot and not reset, causing predictable or repeated random values across restored processes. LIMITING FACTORS: default Node.js deployments that do not use startup snapshots are not affected; impact is limited to Low confidentiality and Low integrity with no availability impact; and the CVSS AC:H reflects additional conditions beyond the attacker's control. The precise trigger beyond the snapshot/random-cache relationship is not described in the available sources.

Severity signals are moderate and broadly consistent. The supplied CVSS 3.0 base score is 4.8 (Medium) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, and the CWE is CWE-330 (use of insufficiently random values), matching the commit title 'crypto: reset random caches across snapshots.' There is no CISA KEV listing, so this is not confirmed actively exploited; the input lists a gist as an exploit reference, so a public PoC reference exists but it is not verified as working exploit code. No EPSS score was provided in the input, so exploitation probability cannot be quantified here - this is a gap. The vuln.today decision label is 'this_month,' and AC:H plus the snapshot-specific nature of the fix indicate the weakness only manifests in applications that use Node.js startup snapshots rather than in default deployments. Net assessment: a real but contained priority - genuine because predictable randomness undermines crypto-derived secrets, but contained because it is tied to a non-default feature and carries only Low confidentiality and integrity impact with no availability impact. Treat it as scheduled (monthly-cadence) patching rather than an emergency, consistent with the decision label.

A Node.js application is built and distributed using a startup snapshot (for example via --build-snapshot/--snapshot-blob or a single-executable application), and because the crypto random cache was not reset when the snapshot was created, every process restored from that snapshot reuses the same cached random bytes. An attacker who can observe or predict secrets derived at startup - such as session tokens, nonces, IVs, or keys - could collide or forecast them across instances, weakening confidentiality and integrity. A gist is referenced as an exploit, but it is not verified as working exploit code.