CVE-2026-73567

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)🟡 PoC Available

Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock · Advisory · JuneAndGreen/sm-crypto · GitHub

https://github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-vh45-f885-3848
github_commit

commit 1f9bd7bd160c (JuneAndGreen/sm-crypto)

Fix landed in JuneAndGreen/sm-crypto commit 1f9bd7bd160c — awaiting tagged release

https://github.com/JuneAndGreen/sm-crypto/commit/1f9bd7bd160c24efd9c26c8f7fda997c68c823d0

Vendor Advisories for CVE-2026-73567(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
sm-crypto—
  • every version up to 0.5.0: fixed in 0.5.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 17:39 UTCEG score recompute
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 18:57 UTCEG score recompute
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-05 02:37 UTCEG score recompute
  9. 2026-10-04 23:22 UTCEPSS rescore
  10. 2026-10-03 19:47 UTCEG score recompute
  11. 2026-10-03 14:26 UTCEPSS rescore
  12. 2026-10-02 21:52 UTCEG score recompute
  13. 2026-10-02 07:32 UTCEG score recompute
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-09-30 21:46 UTCEG score recompute
  16. 2026-09-29 15:24 UTCEPSS rescore
  17. 2026-09-29 03:52 UTCEG score recompute
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-27 16:51 UTCEG score recompute
  20. 2026-09-27 13:48 UTCEPSS rescore
  21. 2026-09-27 09:43 UTCEG score recompute
  22. 2026-09-26 15:59 UTCEPSS rescore
  23. 2026-09-25 03:32 UTCEG score recompute
  24. 2026-09-23 20:49 UTCEG score recompute
  25. 2026-09-23 17:54 UTCEPSS rescore
Show 75 more
  1. 2026-09-22 21:00 UTCEG score recompute
  2. 2026-09-22 01:04 UTCEG score recompute
  3. 2026-09-21 21:09 UTCEPSS rescore
  4. 2026-09-21 00:35 UTCEG score recompute
  5. 2026-09-20 20:16 UTCEPSS rescore
  6. 2026-09-19 16:18 UTCEG score recompute
  7. 2026-09-18 20:35 UTCEG score recompute
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 22:18 UTCEG score recompute
  10. 2026-09-16 23:59 UTCEG score recompute
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 06:34 UTCEG score recompute
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 06:22 UTCEG score recompute
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-13 19:18 UTCEG score recompute
  17. 2026-09-12 17:14 UTCEG score recompute
  18. 2026-09-12 15:02 UTCEPSS rescore
  19. 2026-09-11 18:17 UTCEG score recompute
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 13:57 UTCEG score recompute
  22. 2026-09-10 10:17 UTCEG score recompute
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-09 04:56 UTCEG score recompute
  25. 2026-09-08 22:01 UTCEPSS rescore
  26. 2026-09-07 16:31 UTCEG score recompute
  27. 2026-09-06 15:37 UTCEG score recompute
  28. 2026-09-06 13:48 UTCEPSS rescore
  29. 2026-09-05 17:58 UTCEG score recompute
  30. 2026-09-04 16:42 UTCEG score recompute
  31. 2026-09-04 07:57 UTCEG score recompute
  32. 2026-09-04 05:07 UTCEPSS rescore
  33. 2026-09-02 23:11 UTCEG score recompute
  34. 2026-09-02 14:12 UTCEPSS rescore
  35. 2026-09-01 16:22 UTCEG score recompute
  36. 2026-09-01 13:54 UTCEPSS rescore
  37. 2026-09-01 06:16 UTCEG score recompute
  38. 2026-09-01 04:40 UTCEPSS rescore
  39. 2026-09-01 04:40 UTCEPSS rescore
  40. 2026-08-30 22:27 UTCEG score recompute
  41. 2026-08-30 19:18 UTCEPSS rescore
  42. 2026-08-30 19:17 UTCEPSS rescore
  43. 2026-08-30 05:08 UTCEG score recompute
  44. 2026-08-30 01:22 UTCEPSS rescore
  45. 2026-08-29 07:33 UTCEG score recompute
  46. 2026-08-28 21:42 UTCEPSS rescore
  47. 2026-08-27 19:32 UTCEG score recompute
  48. 2026-08-27 14:25 UTCEPSS rescore
  49. 2026-08-26 15:28 UTCEG score recompute
  50. 2026-08-26 14:47 UTCEPSS rescore
  51. 2026-08-25 17:47 UTCEG score recompute
  52. 2026-08-25 13:49 UTCEPSS rescore
  53. 2026-08-24 15:42 UTCEG score recompute
  54. 2026-08-24 11:14 UTCEG score recompute
  55. 2026-08-23 00:31 UTCEG score recompute
  56. 2026-08-23 00:19 UTCEPSS rescore
  57. 2026-08-22 02:53 UTCEG score recompute
  58. 2026-08-21 23:49 UTCEPSS rescore
  59. 2026-08-21 00:44 UTCEG score recompute
  60. 2026-08-20 22:56 UTCEPSS rescore
  61. 2026-08-19 18:27 UTCEG score recompute
  62. 2026-08-19 17:04 UTCEPSS rescore
  63. 2026-08-18 15:02 UTCEG score recompute
  64. 2026-08-18 13:49 UTCEPSS rescore
  65. 2026-08-18 13:49 UTCEPSS rescore
  66. 2026-08-17 16:44 UTCEG score recompute
  67. 2026-08-17 13:47 UTCEPSS rescore
  68. 2026-08-16 19:08 UTCEG score recompute
  69. 2026-08-16 14:56 UTCEPSS rescore
  70. 2026-08-16 14:56 UTCEPSS rescore
  71. 2026-08-16 06:09 UTCEG score recompute
  72. 2026-08-16 02:15 UTCEPSS rescore
  73. 2026-08-15 04:15 UTCEG score recompute
  74. 2026-08-15 01:31 UTCEPSS rescore
  75. 2026-08-14 19:36 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73567?
CVE-2026-73567 is a critical vulnerability published on August 13, 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…
When was CVE-2026-73567 disclosed?
CVE-2026-73567 was first published on August 13, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73567 actively exploited?
CVE-2026-73567 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73567?
CVE-2026-73567 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73567?
A fix for CVE-2026-73567 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73567 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73567

Explore →

Is Your Infrastructure Affected by CVE-2026-73567?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs