Signature forgery via disabled default SM3 hashing
Published Jan 22, 2026 · Updated Jan 22, 2026
Improper SM2 signature verification in JuneAndGreen sm-crypto before 0.4.0 allows remote attackers to forge signatures for arbitrary public keys. The doVerifySignature function leaves the hash option disabled by default, treating attacker-controlled message bytes as the SM2 digest instead of hashing them with SM3. The default path requires no privileges or user interaction and lets forged signatures pass integrity checks; redundant message formats can retain a chosen prefix.
Summary
What happened
Improper SM2 signature verification in JuneAndGreen sm-crypto before 0.4.0 allows remote attackers to forge signatures for arbitrary public keys. The doVerifySignature function leaves the hash option disabled by default, treating attacker-controlled message bytes as the SM2 digest instead of hashing them with SM3. The default path requires no privileges or user interaction and lets forged signatures pass integrity checks; redundant message formats can retain a chosen prefix.
The record
- CVE
- CVE-2026-23965
- Published
- Jan 22, 2026
- Updated
- Jan 22, 2026
- Vendor
- JuneAndGreen
- Product
- sm-crypto
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2026CVE publishedPublication date reported by the CVE source.
- Jan 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo