CVE-2026-23967
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. A signature malleability vulnerability exists in the SM2 signature verification logic of the sm-crypto library prior to version 0.3.14. An attacker can derive a new valid signature for a previously signed message from an existing signature. Version 0.3.14 patches the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe sm-crypto library has a signature malleability vulnerability in its SM2 signature verification logic. An attacker can derive a new valid signature for a previously signed message from an existing signature without knowing the private key, allowing signature reuse or manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.3.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate sm-crypto in dependenciesSearch your project dependencies file (package.json, yarn.lock, package-lock.json, or npm list) for the sm-crypto packageAffected if sm-crypto is listed as a dependency
-
Determine installed versionRun npm list sm-crypto or check the version field in node_modules/sm-crypto/package.json to get the exact installed versionAffected if The installed version is below 0.3.14
-
Identify SM2 signature usageSearch your codebase for calls to sm-crypto functions related to SM2 verification, such as sm2.verify, crypto.verify, or similar SM2 verification methodsAffected if SM2 signature verification is performed using this library
-
Inspect verification implementationReview the code paths that perform SM2 signature verification to confirm they use the sm-crypto library's verify functionAffected if The vulnerable sm-crypto verify function is being called
You are affected if sm-crypto version below 0.3.14 is installed and your code performs SM2 signature verification using this library.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.3.14
Upgrade sm-crypto to version 0.3.14 or later to obtain the patched library with canonical signature verification.
sm-crypto version 0.3.14
- Check current version of sm-crypto in your project using 'npm list sm-crypto'
- Update to version 0.3.14 or later by running 'npm install [email protected]' or 'npm install sm-crypto@latest'
- Verify the upgrade was successful by running 'npm list sm-crypto' and confirming version 0.3.14 or higher is installed
- If using a lock file, run 'npm update sm-crypto' to update the lockfile and commit changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23967 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data