CVE-2026-23965: sm-crypto Affected by Signature Forgery in SM2-DSA
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.
Published Jan 21, 2026 · Updated Jan 22, 2026
Affected packages
sm-crypto
- Ecosystem
- npm
- Affected
- < 0.4.0
- Fixed in
- 0.4.0
- Check
npm ls sm-crypto
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
Credited to XlabAITeam, A7um, tl2cents, keenanwgn.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-73567
sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock
critical9.1Jul 24, 2026CVE-2026-23966
sm-crypto Affected by Private Key Recovery in SM2-PKE
critical9.1Jan 21, 2026CVE-2026-23967
sm-crypto Affected by Signature Malleability in SM2-DSA
high7.5Jan 21, 2026
