VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

sm-crypto: vulnerability history, versions and safety

sm-crypto is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 38 releases, from Jan 2026 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sm-crypto vulnerabilities

Vulert verdict on sm-crypto 0.5.7 i

Updated on 23 Oct 2026

Good news: 0.5.7, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 65/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 0.5.7 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.5.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.5.7 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 12 packages i
  • Stars 1,163 i
  • OpenSSF scorecard 2/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for sm-crypto, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.5.7 24 Aug 2026 none MIT — Details →
0.5.6 17 Aug 2026 none MIT — Details →
0.5.5 04 Aug 2026 none MIT — Details →
0.5.4 31 Jul 2026 none MIT — Details →
0.5.3 23 Jul 2026 none MIT — Details →
0.5.2 23 Jul 2026 none MIT — Details →
0.5.1 23 Jul 2026 none MIT — Details →
0.5.0 23 Jul 2026 none MIT — Details →
0.4.0 20 Jan 2026 C1 MIT Yes Details →
0.3.14 20 Jan 2026 C1 H1 MIT Yes Details →
0.3.13 16 Oct 2023 C2 H2 MIT Yes Details →
0.3.12 31 Jan 2023 C2 H2 MIT Yes Details →
0.3.11 23 Aug 2022 C2 H2 MIT Yes Details →
0.3.10 18 Jul 2022 C2 H2 MIT Yes Details →
0.3.9 18 Jul 2022 C2 H2 MIT Yes Details →
0.3.8 28 Apr 2022 C2 H2 MIT Yes Details →
0.3.7 06 Dec 2021 C2 H2 MIT Yes Details →
0.3.6 27 Sep 2021 C2 H2 MIT Yes Details →
0.3.5 31 Aug 2021 C2 H2 MIT Yes Details →
0.3.4 26 Aug 2021 C2 H2 MIT Yes Details →
0.3.3 26 Aug 2021 C2 H2 MIT Yes Details →
0.3.2 26 Jul 2021 C2 H2 MIT Yes Details →
0.3.1 26 Jul 2021 C2 H2 MIT Yes Details →
0.3.0 17 May 2021 C2 H2 MIT Yes Details →
0.2.7 25 Apr 2021 C2 H2 MIT Yes Details →
0.2.6 25 Apr 2021 C2 H2 MIT Yes Details →
0.2.5 10 Mar 2021 C2 H2 MIT Yes Details →
0.2.4 26 Feb 2021 C2 H2 MIT Yes Details →
0.2.3 26 Feb 2021 C2 H2 MIT Yes Details →
0.2.2 26 Feb 2021 C2 H2 MIT Yes Details →
0.2.1 14 Sep 2020 C2 H2 MIT Yes Details →
0.2.0 11 Sep 2020 C2 H2 MIT Yes Details →
0.1.4 24 Aug 2020 C2 H2 MIT Yes Details →
0.1.3 24 Aug 2020 C2 H2 MIT Yes Details →
0.1.2 24 Jun 2020 C2 H2 MIT Yes Details →
0.1.1 20 Apr 2020 C2 H2 MIT Yes Details →
0.1.0 26 Sep 2019 C2 H2 MIT Yes Details →
0.0.9 24 Jul 2019 C2 H2 MIT Yes Details →
0.0.8 26 Dec 2018 C2 H2 MIT Yes Details →
0.0.7 18 Dec 2018 C2 H2 MIT Yes Details →
0.0.6 15 Sep 2018 C2 H2 MIT Yes Details →
0.0.5 20 Aug 2018 C2 H2 MIT Yes Details →
0.0.4 28 Jan 2018 C2 H2 MIT Yes Details →
0.0.3 28 Jan 2018 C2 H2 MIT Yes Details →
0.0.2 28 Jan 2018 C2 H2 MIT Yes Details →
0.0.1 28 Jan 2018 C2 H2 MIT Yes Details →

All 46 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for sm-crypto

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-23966: sm-crypto Private Key Recovery Vulnerability 9.1 critical 0.3.14 21 Jan 2026
Predictable Key Generation Vulnerability in sm-crypto Package 9.1 critical 0.5.0 24 Jul 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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About sm-crypto

Is sm-crypto safe to use?

Vulert records 4 vulnerabilities for sm-crypto in npm: 2 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is sm-crypto's Vulert package health score?

Vulert scores sm-crypto 65/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of sm-crypto affected?

No. 0.5.7, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of sm-crypto should I use?

0.5.7 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does sm-crypto have?

4 vulnerabilities are recorded for sm-crypto in the npm ecosystem: 2 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sm-crypto vulnerabilities disclosed?

4 vulnerabilities were recorded for sm-crypto in the last 12 months, and the oldest entry in this database dates to 21 Jan 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sm-crypto are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.