Skip to content

CVE-2026-73567 sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock

CriticalCVSS 9.1 EPSS 0.44%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: total

Description

sm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. Prior to 0.5.0, the default no-argument sm2.generateKeyPairHex() path in Node.js uses the module-wide SecureRandom instance in src/sm2/utils.js, supplied by jsbn@1.1.0, which seeds an ARC4 stream from Math.random() and new Date().getTime() because window.crypto.getRandomValues is unavailable even though globalThis.crypto exists. An attacker who can observe the process's Math.random() outputs and estimate the key-generation time can reconstruct the seed, recover generated SM2 private keys, and predict signing ephemeral scalars used to forge signatures. This issue is fixed in version 0.5.0.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
npm sm-crypto(npm) < 0.5.0 0.5.0 Fixed
JuneAndGreen sm-crypto = < 0.5.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
JuneAndGreen sm-crypto = < 0.5.0 No fix listed
npm sm-crypto(npm) < 0.5.0 0.5.0

References