CVE-2026-73567CWE-338

CVE-2026-73567

Critical · published August 13, 2026

CVSS v3.1
9.1
EPSS
0%
Percentile
24.7
In the wild
Unconfirmed
What it is

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 [email protected], 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.

The record
Technical detail
CVSS v3.1
9.1 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00321 · 24.7th percentile
Weakness
CWE-338 · Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Published
2026-08-13T22:18Z
References (2)
EPSS history
Timeline
  • 13 AUG 17:40Z
    sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock
    cvelistv5