Is CVE-2026-23967 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-23967 being exploited in the wild.

How severe is CVE-2026-23967?

Low severity, with a CVSS score of 3.1, published 21 January 2026.

Which products and versions are affected?

sm-crypto (npm) SEMVER:introduced=0,fixed=0.3.14.

Is there a fix for CVE-2026-23967?

Yes. sm-crypto (npm): upgrade to 0.3.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-23967 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-23967?

Check whether you run sm-crypto (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-23967: sm-crypto signature malleability in SM2-DSA

CVE-2026-23967 · Severity: low · CVSS 3.1 · Published 2026-01-21

sm-crypto is a JavaScript library that implements Chinese cryptographic algorithms, including SM2 digital signatures. A signature malleability flaw allows an attacker to forge alternate valid signatures for previously signed messages without knowing the private key, undermining the authenticity guarantees of any system relying on SM2 signatures for transaction validation, contract enforcement, or audit trails.

Technologies: sm-crypto (npm). Vendors: npm.

Quick answers

Is CVE-2026-23967 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-23967 being exploited in the wild.
How severe is CVE-2026-23967?: Low severity, with a CVSS score of 3.1, published 21 January 2026.
Which products and versions are affected?: sm-crypto (npm) SEMVER:introduced=0,fixed=0.3.14.
Is there a fix for CVE-2026-23967?: Yes. sm-crypto (npm): upgrade to 0.3.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-23967 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-23967?: Check whether you run sm-crypto (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

sm-crypto (npm): upgrade to 0.3.14 or later
```
npm install sm-crypto@0.3.14
```

Technical details

The vulnerability is a signature malleability issue in SM2 signature verification (CWE-347: Improper Verification of Cryptographic Signature). An attacker can derive a new valid signature from an existing valid signature for the same message, exploiting a flaw in the SM2-DSA implementation. The attack is network-reachable and requires no authentication or user interaction. An attacker can forge signatures to bypass integrity checks, impersonate legitimate signers, or create duplicate transactions. The vulnerability was patched in version 0.3.14; all earlier versions are affected.

Affected products

JuneAndGreen sm-crypto < 0.3.14

Identifiers

CVE-2026-23967
GHSA-qv7w-v773-3xqm

Timeline

2026-01-21: disclosed: Advisory GHSA-qv7w-v773-3xqm published
2026-01-21: patched: Version 0.3.14 fixes the vulnerability

References

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.