CVE-2026-23965: Sm crypto Sm-crypto Affected By Signature Forgery Vulnerability

HIGH
Advisory Identifier: GHSA-hpwg-xg7m-3p6m
Share
CVSS 7.5
CWE-347
Published
Advisory Summary

CVE-2026-23965 is a HIGH (CVSS 7.5) sm-crypto affected by signature forgery vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Sm crypto libraries in the npm ecosystem. The issue involves sm-crypto affected by signature forgery in sm2-dsa. Remediation is available by upgrading affected packages to version 0.4.0.

CVE-2026-23965 at a Glance

CVE Identifier CVE-2026-23965
GHSA Identifier GHSA-hpwg-xg7m-3p6m
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Sm crypto
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

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:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-23965

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.

sm-crypto fixed: 0.4.0 
npm install sm-crypto@0.4.0
Verify Direct and Transitive Dependencies

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-23965, 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.4.0), 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-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for 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

### Summary A signature forgery vulnerability exists in the SM2 signature verification logic of sm-crypto. Under default configurations, an attacker can forge valid signatures for arbitrary public keys. If the message space contains sufficient redundancy, the attacker can fix the prefix of the message associated with the forged signature to satisfy specific formatting requirements. ### Credit This vulnerability was discovered by: - XlabAI Team of Tencent Xuanwu Lab - Atuin Automated Vulnerability Discovery Engine

CVE-2026-23965 Affected Sm crypto Versions

1 component(s)
Fixed Versions:
0.4.0
Product / Package Ecosystem Affected Versions Fixed Version
sm-crypto
npm/sm-crypto
npm
< 0.4.0
0.4.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-hpwg-xg7m-3p6m
NVD — CVE-2026-23965 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-23965
Security Fix Commit FIX COMMIT
https://github.com/JuneAndGreen/sm-crypto/commit/85295a859d0766222d12ce2be3e6fce7b438b510
Sm crypto Source Repository REPOSITORY
https://github.com/JuneAndGreen/sm-crypto

Frequently Asked Questions

What is CVE-2026-23965?
CVE-2026-23965 is a security vulnerability in Sm crypto involving sm-crypto Affected by Signature Forgery in SM2-DSA under CWE-347: Improper Verification of Cryptographic Signature.
Which Sm crypto versions are affected?
Affected versions include releases prior to 0.4.0 across affected packages: sm-crypto.
What version fixes CVE-2026-23965?
Upgrading to 0.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is sm-crypto affected?
Yes, sm-crypto is affected in releases prior to 0.4.0. Upgrade your dependency to 0.4.0 or later.
What is the CVSS score of CVE-2026-23965?
CVE-2026-23965 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-23965?
CVE-2026-23965 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check npm dependencies for CVE-2026-23965?
Run the dependency tree command: 'npm ls sm-crypto'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hpwg-xg7m-3p6m",
  "modified" : "2026-01-22T15:43:29Z",
  "published" : "2026-01-21T16:13:44Z",
  "aliases" : [ "CVE-2026-23965" ],
  "summary" : "sm-crypto Affected by Signature Forgery in SM2-DSA",
  "details" : "### Summary\n\nA signature forgery vulnerability exists in the SM2 signature verification logic of sm-crypto. Under default configurations, an attacker can forge valid signatures for arbitrary public keys. If the message space contains sufficient redundancy, the attacker can fix the prefix of the message associated with the forged signature to satisfy specific formatting requirements.\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:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "sm-crypto"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-hpwg-xg7m-3p6m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-23965"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/JuneAndGreen/sm-crypto/commit/85295a859d0766222d12ce2be3e6fce7b438b510"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/JuneAndGreen/sm-crypto"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-21T16:13:44Z",
    "nvd_published_at" : "2026-01-22T03:15:46Z"
  }
}