CVE-2026-73567
Insecure RNG in sm-crypto allows SM2 private key recovery and signature forgeries.
Is CVE-2026-73567 being exploited?
Not confirmed. CVE-2026-73567 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-73567?
CVE-2026-73567 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73567?
Yes. A fix has been recorded for CVE-2026-73567. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73567 affect?
CVE-2026-73567 affects sm-crypto < 0.5.0 (Node.js), Applications using sm2.generateKeyPairHex() no-arg, Services performing SM2 signing/verification. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73567?
Upgrade sm-crypto to >=0.5.0, regenerate and revoke affected SM2 keys.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers who observe Math.random() and estimate key-gen time can reconstruct seeds, recover SM2 private keys, and forge SM2 signatures.
Immediate action required
- affected< 0.5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.