CVE-2026-23966 — Vulnerability in sm-crypto — CVE Details
sm-crypto Affected by Private Key Recovery in SM2-PKE
Summary
Advisory Timeline
- First published January 21, 2026 (264 days ago).
- Last revised February 3, 2026 — 12 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
npm install sm-crypto@0.3.14
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: npm (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| sm-crypto | npm | All versions | 0.3.14 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-345Insufficient Verification of Data AuthenticityMITRE
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 9.1 score means for each attack dimension.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Frequently Asked Questions
- What is CVE-2026-23966?
- sm-crypto Affected by Private Key Recovery in SM2-PKE This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.1/10).
- How do I check if my project is affected by CVE-2026-23966?
- CVE-2026-23966 affects sm-crypto. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-23966 and 200,000+ other known vulnerabilities.
Severity & Exploitability
Exploitation is straightforward and causes maximum impact. Patch immediately.
Also Known As
Related CVEs
- CVE-2026-73567CRITICAL
sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock
- CVE-2026-107722CRITICAL
fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusion
- CVE-2026-108261CRITICAL
TinaCMS admin preview iframe loads an attacker-controlled origin from the URL fragment
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies