VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

secp256k1: vulnerability history, versions and safety

secp256k1 is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all secp256k1 vulnerabilities

Vulert verdict on secp256k1 5.0.2 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 5.0.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 21 Oct 2024 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 1,835 packages i
  • Stars 360 i
  • OpenSSF scorecard 2/10 i
  • Last release 2 months 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 secp256k1, 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
5.0.2 07 Aug 2026 none MIT — Details →
4.0.5 07 Aug 2026 none MIT — Details →
3.8.1 20 Oct 2024 none MIT — Details →
4.0.4 18 Oct 2024 none MIT — Details →
5.0.1 18 Oct 2024 none MIT — Details →
5.0.0 31 Dec 2022 H1 MIT Yes Details →
4.0.3 08 Jan 2022 none MIT — Details →
4.0.2 20 Jul 2020 none MIT — Details →
4.0.1 27 Apr 2020 none MIT — Details →
4.0.0 09 Jan 2020 none MIT — Details →
3.8.0 19 Dec 2019 none MIT — Details →
3.7.1 31 May 2019 none MIT — Details →
3.7.0 08 May 2019 none MIT — Details →
3.6.2 28 Jan 2019 none MIT — Details →
3.6.1 29 Dec 2018 none MIT — Details →
3.6.0 24 Dec 2018 none MIT — Details →
3.5.2 22 Aug 2018 none MIT — Details →
3.5.0 26 Jan 2018 none MIT — Details →
3.4.0 02 Dec 2017 none MIT — Details →
3.3.1 06 Nov 2017 none MIT — Details →
3.3.0 07 Jun 2017 none MIT — Details →
3.2.5 07 Jan 2017 none MIT — Details →
3.2.2 26 Oct 2016 none MIT — Details →
3.2.0 18 Aug 2016 none MIT — Details →
3.1.0 04 May 2016 none MIT — Details →
3.0.1 01 Mar 2016 none MIT — Details →
3.0.0 01 Feb 2016 none MIT — Details →
2.0.10 20 Jan 2016 none MIT — Details →
2.0.9 20 Jan 2016 none MIT — Details →
2.0.8 14 Jan 2016 none MIT — Details →
2.0.7 27 Nov 2015 none MIT — Details →
2.0.6 20 Nov 2015 none MIT — Details →
2.0.5 16 Nov 2015 none MIT — Details →
2.0.4 13 Nov 2015 none MIT — Details →
2.0.3 11 Nov 2015 none MIT — Details →
2.0.2 06 Nov 2015 none MIT — Details →
2.0.1 06 Nov 2015 none MIT — Details →
2.0.0 05 Nov 2015 none MIT — Details →
1.1.6 24 Oct 2015 none MIT — Details →
1.1.5 22 Oct 2015 none MIT — Details →
1.1.4 21 Sep 2015 none MIT — Details →
1.1.3 15 Sep 2015 none MIT — Details →
1.1.2 15 Sep 2015 none MIT — Details →
1.1.1 09 Aug 2015 none MIT — Details →
1.1.0 07 Aug 2015 none MIT — Details →
1.0.1 07 Aug 2015 none MIT — Details →
1.0.0 06 Aug 2015 none MIT — Details →
0.0.17 02 Jul 2015 none MIT — Details →
0.0.16 27 Jun 2015 none MIT — Details →
0.0.15 28 Jan 2015 none MIT — Details →
0.0.14 22 Jan 2015 none MIT — Details →
0.0.13 22 Dec 2014 none MIT — Details →
0.0.12 13 Nov 2014 none non-standard — Details →
0.0.11 13 Nov 2014 none non-standard — Details →
0.0.10 10 Nov 2014 none non-standard — Details →
0.0.9 07 Nov 2014 none non-standard — Details →
0.0.8 02 Nov 2014 none non-standard — Details →
0.0.7 26 Oct 2014 none non-standard — Details →
0.0.6 13 Oct 2014 none non-standard — Details →
0.0.5 12 Oct 2014 none non-standard — Details →
0.0.4 11 Oct 2014 none non-standard — Details →
0.0.3 06 Oct 2014 none non-standard — Details →
0.0.2 05 Oct 2014 none non-standard — Details →
0.0.1 05 Oct 2014 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for secp256k1

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-48930: secp256k1 Vulnerability Allows Private Key Extraction Over ECDH 8.7 high 5.0.1 21 Oct 2024

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 secp256k1

Is secp256k1 safe to use?

Vulert records 1 vulnerabilities for secp256k1 in npm: 0 critical, 1 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 secp256k1's Vulert package health score?

Vulert scores secp256k1 75/100, which reads as in good shape. 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 secp256k1 affected?

No. 5.0.2, 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 secp256k1 should I use?

5.0.2 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 secp256k1 have?

1 vulnerability is recorded for secp256k1 in the npm ecosystem: 0 critical, 1 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 secp256k1 vulnerabilities disclosed?

0 vulnerabilities were recorded for secp256k1 in the last 12 months, and the oldest entry in this database dates to 21 Oct 2024. 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 secp256k1 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 secp256k1 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the secp256k1 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.