VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

node-fetch: vulnerability history, versions and safety

node-fetch is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 24 releases, from Sep 2020 to Aug 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M1 L1
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 node-fetch vulnerabilities

Vulert verdict on node-fetch 3.3.2 i

Updated on 22 Oct 2026

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

Package health score 74/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.3.2 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 02 Aug 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 57,959 packages i
  • Stars 8,848 i
  • OpenSSF scorecard 3/10 i
  • Last release 38 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 node-fetch, 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
2.7.0 23 Aug 2023 none MIT — Details →
2.6.13 18 Aug 2023 none MIT — Details →
3.3.2 25 Jul 2023 none MIT — Details →
2.6.12 29 Jun 2023 none MIT — Details →
2.6.11 09 May 2023 none MIT — Details →
2.6.10 08 May 2023 none MIT — Details →
3.3.1 11 Mar 2023 none MIT — Details →
2.6.9 30 Jan 2023 none MIT — Details →
2.6.8 13 Jan 2023 none MIT — Details →
3.3.0 10 Nov 2022 none MIT — Details →
3.2.10 31 Jul 2022 none MIT — Details →
3.2.9 18 Jul 2022 M1 MIT Yes Details →
3.2.8 12 Jul 2022 M1 MIT Yes Details →
3.2.7 11 Jul 2022 M1 MIT Yes Details →
3.2.6 09 Jun 2022 M1 MIT Yes Details →
3.2.5 01 Jun 2022 M1 MIT Yes Details →
3.2.4 28 Apr 2022 M1 MIT Yes Details →
3.2.3 11 Mar 2022 M1 MIT Yes Details →
3.2.2 07 Mar 2022 M1 MIT Yes Details →
3.2.1 01 Mar 2022 M1 MIT Yes Details →
4.0.0-beta.4 27 Jan 2022 none MIT — Details →
4.0.0-beta.3 27 Jan 2022 none MIT — Details →
4.0.0-beta.2 27 Jan 2022 none MIT — Details →
4.0.0-beta.1 27 Jan 2022 none MIT — Details →
3.2.0 20 Jan 2022 M1 MIT Yes Details →
3.1.1 16 Jan 2022 M1 MIT Yes Details →
2.6.7 16 Jan 2022 none MIT — Details →
3.1.0 08 Nov 2021 H1 M1 MIT Yes Details →
2.6.6 31 Oct 2021 none MIT — Details →
2.6.5 22 Sep 2021 none MIT — Details →
2.6.4 21 Sep 2021 none MIT — Details →
2.6.3 20 Sep 2021 none MIT — Details →
2.6.2 06 Sep 2021 none MIT — Details →
3.0.0 31 Aug 2021 H1 M1 MIT Yes Details →
3.0.0-beta.10 19 Jul 2021 none MIT — Details →
2.6.1 05 Sep 2020 none MIT — Details →
3.0.0-beta.9 05 Sep 2020 none MIT — Details →
3.0.0-beta.8 10 Aug 2020 none MIT — Details →
3.0.0-beta.7 11 Jun 2020 none MIT — Details →
3.0.0-beta.6-exportfix 25 May 2020 none MIT — Details →
3.0.0-beta.6 25 May 2020 none MIT — Details →
3.0.0-beta.5 22 Apr 2020 none MIT — Details →
3.0.0-beta.4 14 Mar 2020 none MIT — Details →
3.0.0-beta.3 13 Mar 2020 none MIT — Details →
3.0.0-beta.2 13 Mar 2020 none MIT — Details →
3.0.0-beta.1 13 Mar 2020 none MIT — Details →
2.6.0 16 May 2019 L1 MIT Yes Details →
2.5.0 01 May 2019 L1 MIT Yes Details →
2.4.1 27 Apr 2019 L1 MIT Yes Details →
2.4.0 26 Apr 2019 L1 MIT Yes Details →
2.3.0 13 Nov 2018 L1 MIT Yes Details →
2.2.1 05 Nov 2018 L1 MIT Yes Details →
2.2.0 22 Jul 2018 L1 MIT Yes Details →
2.1.2 25 Mar 2018 L1 MIT Yes Details →
2.1.1 05 Mar 2018 L1 MIT Yes Details →
2.1.0 05 Mar 2018 L1 MIT Yes Details →
2.0.0 03 Feb 2018 L1 MIT Yes Details →
2.0.0-alpha.9 24 Sep 2017 none MIT — Details →
1.7.3 08 Sep 2017 none MIT — Details →
1.7.2 08 Aug 2017 none MIT — Details →
2.0.0-alpha.8 26 Jul 2017 none MIT — Details →
2.0.0-alpha.7 25 Jul 2017 none MIT — Details →
2.0.0-alpha.6 21 Jul 2017 none MIT — Details →
2.0.0-alpha.5 03 Jun 2017 none MIT — Details →
1.7.1 03 Jun 2017 none MIT — Details →
1.7.0 23 May 2017 none MIT — Details →
2.0.0-alpha.4 15 May 2017 none MIT — Details →
2.0.0-alpha.3 29 Jan 2017 none MIT — Details →
2.0.0-alpha.1 15 Jan 2017 none MIT — Details →
1.6.3 26 Sep 2016 none MIT — Details →
1.6.2 24 Sep 2016 none MIT — Details →
1.6.1 11 Sep 2016 none MIT — Details →
1.6.0 03 Aug 2016 none MIT — Details →
1.5.3 25 May 2016 none MIT — Details →
1.5.2 06 May 2016 none MIT — Details →
1.5.1 12 Apr 2016 none MIT — Details →
1.5.0 05 Apr 2016 none MIT — Details →
1.4.1 23 Mar 2016 none MIT — Details →
1.4.0 19 Mar 2016 none MIT — Details →
1.3.3 28 Sep 2015 none MIT — Details →
1.3.2 22 Jul 2015 none MIT — Details →
1.3.1 11 Jul 2015 none MIT — Details →
1.3.0 04 Jun 2015 none MIT — Details →
1.2.1 04 May 2015 none MIT — Details →
1.2.0 03 May 2015 none MIT — Details →
1.1.2 29 Apr 2015 none MIT — Details →
1.1.1 22 Apr 2015 none MIT — Details →
1.1.0 17 Apr 2015 none MIT — Details →
1.0.6 24 Mar 2015 none MIT — Details →
1.0.5 19 Mar 2015 none MIT — Details →
1.0.4 06 Feb 2015 none MIT — Details →
1.0.3 28 Jan 2015 none MIT — Details →
1.0.2 28 Jan 2015 none MIT — Details →
1.0.1 27 Jan 2015 none MIT — Details →
1.0.0 27 Jan 2015 none MIT — Details →
0.1.0 27 Jan 2015 none MIT — Details →

All 96 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
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for node-fetch

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-0235: node-fetch - Exposure of Sensitive Information to an Unauthorized Actor 8.8 high 3.1.1 21 Jan 2022
CVE-2022-2596: node-fetch Inefficient Regular Expression Complexity 5.9 medium 3.2.10 02 Aug 2022
CVE-2020-15168: Node-fetch size option not honored after redirect 2.6 low 2.6.1 10 Sep 2020

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 node-fetch

Is node-fetch safe to use?

Vulert records 3 vulnerabilities for node-fetch in npm: 0 critical, 1 high, 1 medium and 1 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 node-fetch's Vulert package health score?

Vulert scores node-fetch 74/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 node-fetch affected?

No. 3.3.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 node-fetch should I use?

3.3.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 node-fetch have?

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

How often are new node-fetch vulnerabilities disclosed?

0 vulnerabilities were recorded for node-fetch in the last 12 months, and the oldest entry in this database dates to 10 Sep 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 node-fetch 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 node-fetch for upcoming vulnerabilities?

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