# CVE-2026-23965: sm-crypto Affected by Signature Forgery in SM2-DSA

> Attackers can forge valid SM2 signatures for arbitrary public keys, bypassing authentication or integrity checks in applications using this JavaScript library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2026
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-hpwg-xg7m-3p6m

## What is CVE-2026-23965?

CVE-2026-23965 is a high-severity vulnerability in JuneAndGreen sm-crypto, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

sm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. A signature forgery vulnerability exists in the SM2 signature verification logic of sm-crypto prior to version 0.4.0. 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. Version 0.4.0 patches the issue.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-23965?

2 open source packages ship an affected version, including sm-crypto. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sm-crypto` | npm | All versions | 0.4.0 |
| `sm-crypto` | npm | All versions | 0.4.0 |

Products: Juneandgreen Sm-Crypto.

## How do I fix CVE-2026-23965?

Upgrade sm-crypto to 0.4.0 or later.

## Is CVE-2026-23965 being exploited?

There is no known exploitation of CVE-2026-23965 in the wild and no public exploit code.

## Other vulnerabilities in JuneAndGreen sm-crypto

- [CVE-2026-23966](https://insights.sbomify.com/CVE-2026-23966/): sm-crypto Affected by Private Key Recovery in SM2-PKE (critical 9.1)
- [CVE-2026-23967](https://insights.sbomify.com/CVE-2026-23967/): sm-crypto Affected by Signature Malleability in SM2-DSA (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23965 and fix it if it is affected.

What it is: CVE-2026-23965 is a high-severity vulnerability in JuneAndGreen sm-crypto, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23965 in the wild and no public exploit code.

Affected packages and fixed versions:
- sm-crypto (npm): affected all versions; fixed in 0.4.0
- sm-crypto (npm): affected all versions; fixed in 0.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23965/ (Markdown: https://insights.sbomify.com/CVE-2026-23965/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23965
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23965
- OSV: https://osv.dev/vulnerability/CVE-2026-23965

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23965/
Summaries are generated and may contain mistakes; the official description above is the record.