Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. sm-crypto
  4. ›
  5. CVE-2026-23965

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

January 21, 2026 (updated January 22, 2026)

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.

References

  • github.com/JuneAndGreen/sm-crypto
  • github.com/JuneAndGreen/sm-crypto/commit/85295a859d0766222d12ce2be3e6fce7b438b510
  • github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-hpwg-xg7m-3p6m
  • github.com/advisories/GHSA-hpwg-xg7m-3p6m
  • nvd.nist.gov/vuln/detail/CVE-2026-23965

Code Behaviors & Features

Detect and mitigate CVE-2026-23965 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.4.0

Fixed versions

  • 0.4.0

Solution

Upgrade to version 0.4.0 or above.

Impact 7.5 HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Learn more about CVSS

Weakness

  • CWE-347: Improper Verification of Cryptographic Signature

Source file

npm/sm-crypto/CVE-2026-23965.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 04 Feb 2026 00:35:38 +0000.