Answer in brief
CVE-2026-73567 records a Critical severity (CVSS 9.1) vulnerability in sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock. The current sources do not mark it as known exploited. The current feed maps JuneAndGreen/sm-crypto (generic), sm-crypto (npm), sm-crypto (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps JuneAndGreen/sm-crypto (generic), sm-crypto (npm), sm-crypto (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| JuneAndGreen/sm-cryptogeneric | < 0.5.0 | Not reported |
| sm-cryptonpm | >=0 <0.5.0 | 0.5.0 |
| sm-cryptonpm | <0.5.0 | 0.5.0 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-73567 records a Critical severity (CVSS 9.1) vulnerability in sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock. The current sources do not mark it as known exploited. The current feed maps JuneAndGreen/sm-crypto (generic), sm-crypto (npm), sm-crypto (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps JuneAndGreen/sm-crypto (generic), sm-crypto (npm), sm-crypto (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| JuneAndGreen/sm-cryptogeneric | < 0.5.0 | Not reported |
| sm-cryptonpm | >=0 <0.5.0 | 0.5.0 |
| sm-cryptonpm | <0.5.0 | 0.5.0 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.