npmWorst: Critical4 advisories

sm-crypto: known vulnerabilities

sm-crypto has 4 reviewed security advisories in the GitHub Advisory Database — 2 critical, 2 high. The most recent was published 2026-07-24. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the sm-crypto versions running across your servers, containers and images, and ranks what to patch first.

How to fix sm-crypto

Upgrade sm-crypto to a release at or above the fixed version shown for each advisory below. For npm:

npm install sm-crypto@0.5.0 (or run npm audit fix)

SkyShield checks the installed version on every machine and container, so you can see which hosts are still on an affected release after you roll the fix out.

Advisories (4)

sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock Critical 9.1 CWE-338 — Affected: before 0.5.0. Fixed in 0.5.0. Published 2026-07-24. GHSA-vh45-f885-3848 · CVE-2026-73567
sm-crypto Affected by Signature Forgery in SM2-DSA High 7.5 CWE-347 — Affected: before 0.4.0. Fixed in 0.4.0. Published 2026-01-22. GHSA-hpwg-xg7m-3p6m · CVE-2026-23965
sm-crypto Affected by Private Key Recovery in SM2-PKE Critical 9.1 CWE-345 — Affected: before 0.3.14. Fixed in 0.3.14. Published 2026-01-22. GHSA-pgx9-497m-6c4v · CVE-2026-23966
sm-crypto Affected by Signature Malleability in SM2-DSA High 7.5 CWE-347 — Affected: before 0.3.14. Fixed in 0.3.14. Published 2026-01-22. GHSA-qv7w-v773-3xqm · CVE-2026-23967

Find sm-crypto across your fleet

Install one agent per server and connect your cloud. SkyShield matches your packages and images against GHSA, CISA KEV and EPSS and shows the fix per machine. Free for one server, then from $49 per server a month. Start free.