Security readout for executives and security teams
Plain-English summary
CVE-2026-23965 affects the JavaScript sm-crypto library used for Chinese cryptographic algorithms. Versions before 0.4.0 can incorrectly accept forged SM2 signatures. If an application relies on these signatures for identity, approvals, transactions, or data integrity, attackers may bypass trust checks. The vendor advisory states version 0.4.0 fixes the issue.
Executive priority
Treat as a high-priority dependency update for systems that trust SM2 signatures. Business urgency is highest where signature validation protects approvals, identity, financial actions, or regulated data integrity.
Technical view
sm-crypto before 0.4.0 has a CWE-347 signature verification flaw in SM2-DSA. Under default configurations, an attacker can forge valid signatures for arbitrary public keys. The CVSS 3.1 score is 7.5, driven by network reachability, low complexity, no privileges, no user interaction, and high integrity impact.
Likely exposure
Exposure is likely in applications or services that include sm-crypto below 0.4.0 and use SM2 signature verification for trust decisions. Transitive dependency exposure is possible but must be confirmed from package manifests and lockfiles.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is serious because successful forgery can undermine authentication or integrity controls wherever SM2 signatures are trusted.
Researcher notes
Evidence is limited to the CVE record, GitHub advisory, and patch commit. The advisory describes arbitrary-public-key signature forgery and possible message-prefix control when the message space has enough redundancy. Avoid assuming exploit activity or affected downstream products without local dependency evidence.
Mitigation direction
- Upgrade sm-crypto to version 0.4.0 or later.
- Identify direct and transitive sm-crypto usage in JavaScript dependency inventories.
- Prioritize systems where SM2 signatures authorize users, transactions, documents, or API requests.
- Review the GitHub advisory and vendor commit for implementation-specific guidance.
Validation and detection
- Check package manifests and lockfiles for sm-crypto versions below 0.4.0.
- Confirm deployed artifacts use the patched dependency version, not only source repositories.
- Review code paths that call SM2 signature verification for security decisions.
- Run normal application integrity and authentication tests after upgrading.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23965 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-hpwg-xg7m-3p6mCVE reference · x_refsource_CONFIRM
- https://github.com/JuneAndGreen/sm-crypto/commit/85295a859d0766222d12ce2be3e6fce7b438b510CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.