p PatchFirst

CVE-2026-73567

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 9.1 · Critical · EPSS 0.4% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • sm-crypto

    Versions
    • < 0.5.0: Affected

    No fix published

  • sm-crypto npm

    Affected ranges
    • SEMVER: < 0.5.0

    Update to 0.5.0

Original sources

Check your server →