Vulnerability Database · npm · sm-crypto · Version
sm-crypto 0.2.2
0.2.2 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.5.7.
Critical 2 High 2 Medium 0 Low 0 Unrated 0
-
Released 26 Feb 2021
Licence MIT
Also known from other sources 4
Newer releases 46
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
sm-crypto 0.2.2 vulnerabilities
4 vulnerabilities cover sm-crypto 0.2.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Predictable Key Generation Vulnerability in sm-crypto Package | 9.1 critical | 0.5.0 | 24 Jul 2026 |
| CVE-2026-23966: sm-crypto Private Key Recovery Vulnerability | 9.1 critical | 0.3.14 | 21 Jan 2026 |
| CVE-2026-23965: Signature Forgery Vulnerability in sm-crypto Package | 7.5 high | 0.4.0 | 21 Jan 2026 |
| CVE-2026-23967: sm-crypto Signature Malleability Vulnerability | 7.5 high | 0.3.14 | 21 Jan 2026 |
Looking for another version, or everything Vulert holds for sm-crypto?
Questions
About sm-crypto 0.2.2
Is sm-crypto 0.2.2 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover sm-crypto 0.2.2: 2 critical, 2 high, 0 medium and 0 low. The upgrade Vulert recommends is 0.5.7, and each entry above names the fixed version to move to.
Which version of sm-crypto should I use instead of 0.2.2?
0.5.7 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.2.2 the latest release of sm-crypto?
No. 0.2.2 was published 26 Feb 2021, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor sm-crypto for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sm-crypto version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.