CRITICALVulnerability

CVE-2026-73567

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.

Properties

severity
CRITICAL
score
9.1
cve_id
CVE-2026-73567
signal_observed_at
2026-09-18T21:50:18+00:00
vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
published_at
2026-08-13T18:18:19.387
last_modified
2026-09-18T20:09:01.757

Related Entities (2)

HAS_WEAKNESS (1)

[Weakness]Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

DESCRIBED_BY (1)

[Source]NVD

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-73567 — Ninja Signal Threat Intelligence | Ninja Signal