For your digest
sm-crypto: sm-crypto Affected by Signature Malleability in SM2-DSA
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
sm-crypto (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- sm-crypto (npm): every version, before 0.3.14
The fix
sm-crypto (npm) fixed in 0.3.14
npmnpm install sm-crypto@0.3.14pnpmpnpm add sm-crypto@0.3.14yarnyarn add sm-crypto@0.3.14bunbun add sm-crypto@0.3.14Check what is installednpm ls sm-cryptoPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency sm-crypto to 0.3.14 or the nearest later release, to fix CVE-2026-23967. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".