CVE-2026-23967 json
sm-crypto Affected by Signature Malleability in SM2-DSA
published 9mo ago modified 4mo ago also GHSA-qv7w-v773-3xqm , EUVD-2026-3675
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
sm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. A signature malleability vulnerability exists in the SM2 signature verification logic of the sm-crypto library prior to version 0.3.14. An attacker can derive a new valid signature for a previously signed message from an existing signature. Version 0.3.14 patches the issue.
Patch / fix
- npm sm-crypto 0.3.14
- juneandgreen sm-crypto 0.3.14
Is CVE-2026-23967 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 9mo ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | sm-crypto | <0.3.14 |
0.3.14 |
Affected products
- JuneAndGreen sm-crypto
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
github.com
/JuneAndGreen/sm-crypto/security/advisories/GHSA-qv7w-v773-3xqm
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-23967
advisory
-
github.com
/JuneAndGreen/sm-crypto
package
Sources
- CVE List CVE-2026-23967
- GitHub Advisory GHSA-qv7w-v773-3xqm
- NVD CVE-2026-23967
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.