VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

elliptic: vulnerability history, versions and safety

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

i
12 vulnerabilities recorded C1 H1 M1 L9
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 08 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all elliptic vulnerabilities

Vulert verdict on elliptic 6.6.1 i

Updated on 23 Oct 2026

Careful: 6.6.1 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.6.1 — affected i
  • Vulnerabilities on record 12 over 5 years · 1 in the last year i
  • Latest disclosure 08 Jan 2026 i
  • Highest CVSS 9.0 i
  • With no published fix 3 i
  • Depended on by 140,831 packages i
  • Stars 1,768 i
  • OpenSSF scorecard 0/10 i
  • Last release 23 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 elliptic, 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
6.6.1 13 Nov 2024 L3 MIT No Details →
6.6.0 26 Oct 2024 C1 L3 MIT No Details →
6.5.7 14 Aug 2024 C1 L4 MIT No Details →
6.5.6 17 Jul 2024 C1 L7 MIT No Details →
6.5.5 05 Mar 2024 C1 L9 MIT No Details →
6.5.4 02 Feb 2021 C1 L9 MIT No Details →
6.5.3 18 Jun 2020 C1 M1 L9 MIT No Details →
6.5.2 22 Nov 2019 C1 H1 M1 L9 MIT No Details →
6.5.1 04 Sep 2019 C1 H1 M1 L9 MIT No Details →
6.5.0 26 Jun 2019 C1 H1 M1 L9 MIT No Details →
6.4.1 09 Aug 2018 C1 H1 M1 L9 MIT No Details →
6.4.0 22 Feb 2017 C1 H1 M1 L9 MIT No Details →
6.3.3 06 Feb 2017 C1 H1 M1 L9 MIT No Details →
6.3.2 15 Sep 2016 C1 H1 M1 L9 MIT No Details →
6.3.1 14 Jun 2016 C1 H1 M1 L9 MIT No Details →
6.3.0 14 Jun 2016 C1 H1 M1 L9 MIT No Details →
6.2.8 01 Jun 2016 C1 H1 M1 L9 MIT No Details →
6.2.7 25 May 2016 C1 H1 M1 L9 MIT No Details →
6.2.6 25 May 2016 C1 H1 M1 L9 MIT No Details →
6.2.5 20 May 2016 C1 H1 M1 L9 MIT No Details →
6.2.4 20 May 2016 C1 H1 M1 L9 MIT No Details →
6.2.3 29 Jan 2016 C1 H1 M1 L9 MIT No Details →
6.2.2 25 Jan 2016 C1 H1 M1 L9 MIT No Details →
6.2.1 24 Jan 2016 C1 H1 M1 L9 MIT No Details →
6.2.0 22 Jan 2016 C1 H1 M1 L9 MIT No Details →
6.1.0 17 Jan 2016 C1 H1 M1 L9 MIT No Details →
6.0.2 07 Nov 2015 C1 H1 M1 L9 MIT No Details →
6.0.1 02 Nov 2015 C1 H1 M1 L9 MIT No Details →
6.0.0 28 Oct 2015 C1 H1 M1 L9 MIT No Details →
5.2.1 28 Oct 2015 C1 H1 M1 L9 MIT No Details →
5.2.0 23 Oct 2015 C1 H1 M1 L8 MIT No Details →
5.1.0 20 Jul 2015 C1 H1 M1 L8 MIT No Details →
5.0.0 07 Jul 2015 C1 H1 M1 L8 MIT No Details →
4.1.0 04 Jul 2015 C1 H1 M1 L8 MIT No Details →
4.0.0 25 Jun 2015 C1 H1 M1 L8 MIT No Details →
3.1.0 11 Jun 2015 C1 H1 M1 L7 MIT No Details →
3.0.4 03 Jun 2015 C1 H1 M1 L7 MIT No Details →
3.0.3 27 Feb 2015 C1 H1 M1 L7 MIT No Details →
3.0.2 14 Feb 2015 C1 H1 M1 L7 MIT No Details →
3.0.1 09 Feb 2015 C1 H1 M1 L7 MIT No Details →
2.0.2 07 Feb 2015 C1 H1 M1 L7 MIT No Details →
2.0.1 21 Jan 2015 C1 H1 M1 L7 MIT No Details →
2.0.0 18 Jan 2015 C1 H1 M1 L7 MIT No Details →
1.0.1 12 Jan 2015 C1 H1 M1 L6 MIT No Details →
1.0.0 05 Jan 2015 C1 H1 M1 L6 MIT No Details →
0.16.0 02 Jan 2015 C1 H1 M1 L6 MIT No Details →
0.15.17 02 Jan 2015 C1 H1 M1 L6 MIT No Details →
0.15.15 27 Nov 2014 C1 H1 M1 L6 MIT No Details →
0.15.14 05 Nov 2014 C1 H1 M1 L6 MIT No Details →
0.15.13 04 Nov 2014 C1 H1 M1 L6 MIT No Details →
0.15.12 02 Nov 2014 C1 H1 M1 L6 MIT No Details →
0.15.11 25 Sep 2014 C1 H1 M1 L6 MIT No Details →
0.15.10 09 Sep 2014 C1 H1 M1 L6 MIT No Details →
0.15.9 07 Sep 2014 C1 H1 M1 L6 MIT No Details →
0.15.8 27 Aug 2014 C1 H1 M1 L6 MIT No Details →
0.15.7 18 Jun 2014 C1 H1 M1 L6 MIT No Details →
0.15.6 06 Jun 2014 C1 H1 M1 L6 MIT No Details →
0.15.5 31 May 2014 C1 H1 M1 L6 MIT No Details →
0.15.4 31 May 2014 C1 H1 M1 L6 MIT No Details →
0.15.3 27 May 2014 C1 H1 M1 L6 MIT No Details →
0.15.2 27 May 2014 C1 H1 M1 L6 MIT No Details →
0.15.1 25 May 2014 C1 H1 M1 L6 MIT No Details →
0.15.0 25 May 2014 C1 H1 M1 L6 MIT No Details →
0.14.2 24 May 2014 C1 H1 M1 L6 MIT No Details →
0.14.1 23 May 2014 C1 H1 M1 L6 MIT No Details →
0.14.0 23 May 2014 C1 H1 M1 L6 MIT No Details →
0.13.2 21 May 2014 C1 H1 M1 L6 MIT No Details →
0.13.1 18 May 2014 C1 H1 M1 L6 MIT No Details →
0.12.0 17 May 2014 C1 H1 M1 L6 MIT No Details →
0.11.1 17 May 2014 C1 H1 M1 L6 MIT No Details →
0.11.0 16 May 2014 C1 H1 M1 L6 MIT No Details →
0.10.2 10 May 2014 C1 H1 M1 L6 MIT No Details →
0.10.1 09 May 2014 C1 H1 M1 L6 MIT No Details →
0.10.0 08 May 2014 C1 H1 M1 L6 MIT No Details →
0.9.2 05 May 2014 C1 H1 M1 L6 MIT No Details →
0.9.1 05 May 2014 C1 H1 M1 L6 MIT No Details →
0.9.0 05 May 2014 C1 H1 M1 L6 MIT No Details →
0.8.0 04 May 2014 C1 H1 M1 L6 MIT No Details →
0.7.0 29 Apr 2014 C1 H1 M1 L6 MIT No Details →
0.6.1 27 Apr 2014 C1 H1 M1 L6 MIT No Details →
0.6.0 26 Apr 2014 C1 H1 M1 L6 MIT No Details →
0.5.0 26 Apr 2014 C1 H1 M1 L6 MIT No Details →
0.4.0 25 Apr 2014 C1 H1 M1 L6 MIT No Details →
0.3.0 25 Apr 2014 C1 H1 M1 L6 MIT No Details →
0.2.0 25 Apr 2014 C1 H1 M1 L6 MIT No Details →
0.1.0 23 Apr 2014 C1 H1 M1 L6 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2024 8
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for elliptic

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Private Key Extraction Vulnerability in Elliptic Package 9.0 critical 6.6.1 12 Feb 2025
CVE-2020-13822: Signature Malleability in elliptic 7.7 high 6.5.3 29 Jul 2020
CVE-2020-28498: Cryptographic Issues in elliptic Package 6.8 medium 6.5.4 08 Mar 2021
CVE-2025-14505: Elliptic Package Suffers from Risky ECDSA Implementation Leading to Signature Issues 5.6 low No fix published 08 Jan 2026
Signature Malleability Vulnerability in Elliptic Package 6.5.5 5.3 low 6.5.6 10 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 elliptic

Is elliptic safe to use?

Vulert records 12 vulnerabilities for elliptic in npm: 1 critical, 1 high, 1 medium and 9 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is elliptic's Vulert package health score?

Vulert scores elliptic 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of elliptic affected?

Yes. 6.6.1, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of elliptic should I use?

6.6.1 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 elliptic have?

12 vulnerabilities are recorded for elliptic in the npm ecosystem: 1 critical, 1 high, 1 medium and 9 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new elliptic vulnerabilities disclosed?

1 vulnerability was recorded for elliptic in the last 12 months, and the oldest entry in this database dates to 29 Jul 2020. 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 elliptic 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 elliptic for upcoming vulnerabilities?

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