CVE-2026-23966: Sm crypto Sm-crypto Affected By Private Key Vulnerability
CRITICALCVE-2026-23966 is a CRITICAL (CVSS 9.1) sm-crypto affected by private key vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Sm crypto libraries in the npm ecosystem. The issue involves sm-crypto affected by private key recovery in sm2-pke. Remediation is available by upgrading affected packages to version 0.3.14.
CVE-2026-23966 at a Glance
Security Impact
CVSS: 9.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2026-23966
To remediate this vulnerability, upgrade all affected Sm crypto dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install sm-crypto@0.3.14
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls sm-crypto
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-23966, inspect your project dependencies using npm:
npm ls sm-crypto
Analyze the terminal output to locate any version of Sm crypto in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.3.14), your application is affected.
Note: The npm ls sm-crypto command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Sm crypto, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-23966 Affected Sm crypto Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
sm-crypto
|
npm |
< 0.3.14
|
0.3.14
|
References
Frequently Asked Questions
What is CVE-2026-23966?
Which Sm crypto versions are affected?
What version fixes CVE-2026-23966?
Is sm-crypto affected?
What is the CVSS score of CVE-2026-23966?
What CWE is associated with CVE-2026-23966?
How can I check npm dependencies for CVE-2026-23966?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pgx9-497m-6c4v",
"modified" : "2026-01-22T15:43:14Z",
"published" : "2026-01-21T16:13:25Z",
"aliases" : [ "CVE-2026-23966" ],
"summary" : "sm-crypto Affected by Private Key Recovery in SM2-PKE",
"details" : "### Summary\n\nA private key recovery vulnerability exists in the SM2 decryption logic of sm-crypto. By interacting with the SM2 decryption interface multiple times, an attacker can fully recover the private key within approximately several hundred interactions.\n\n\n### Credit\n\nThis vulnerability was discovered by:\n- XlabAI Team of Tencent Xuanwu Lab\n- Atuin Automated Vulnerability Discovery Engine",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "sm-crypto"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.3.14"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-pgx9-497m-6c4v"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-23966"
}, {
"type" : "WEB",
"url" : "https://github.com/JuneAndGreen/sm-crypto/commit/b1c824e58fdf1eaa73692c124a095819a8c45707"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/JuneAndGreen/sm-crypto"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-345" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-01-21T16:13:25Z",
"nvd_published_at" : "2026-01-22T03:15:47Z"
}
}