VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

cross-fetch: vulnerability history, versions and safety

cross-fetch is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 16 releases, first recorded in Apr 2022. 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 M1
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 cross-fetch vulnerabilities

Vulert verdict on cross-fetch 4.1.0 i

Updated on 22 Oct 2026

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

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

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

  • Current release 4.1.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 17 Apr 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 36,195 packages i
  • Stars 1,694 i
  • OpenSSF scorecard 2/10 i
  • Last release 22 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 cross-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
3.2.0 21 Dec 2024 none MIT — Details →
4.1.0 21 Dec 2024 none MIT — Details →
4.0.0 03 Jul 2023 none MIT — Details →
4.0.0-alpha.13 02 Jul 2023 none MIT — Details →
3.1.8 02 Jul 2023 none MIT — Details →
4.0.0-alpha.10 02 Jul 2023 none MIT — Details →
3.1.7 01 Jul 2023 none MIT — Details →
3.1.7-test.0 11 Jun 2023 none MIT — Details →
4.0.0-alpha.5 02 Jun 2023 none MIT — Details →
4.0.0-alpha.4 02 Jun 2023 none MIT — Details →
3.1.6 14 May 2023 none MIT — Details →
2.2.6 10 Apr 2022 none MIT — Details →
3.1.5 20 Jan 2022 none MIT — Details →
3.2.0-alpha.2 19 Oct 2021 none MIT — Details →
3.2.0-alpha.1 19 Oct 2021 none MIT — Details →
3.2.0-alpha.0 19 Oct 2021 none MIT — Details →
2.2.5 25 Jul 2021 none MIT — Details →
2.2.4 25 Jul 2021 none MIT — Details →
3.1.4 02 Apr 2021 M1 MIT Yes Details →
3.1.4-alpha.0 01 Apr 2021 M1 MIT Yes Details →
3.1.3 30 Mar 2021 M1 MIT Yes Details →
3.1.3-alpha.6 28 Mar 2021 M1 MIT Yes Details →
3.1.3-alpha.5 28 Mar 2021 M1 MIT Yes Details →
3.1.3-alpha.4 28 Mar 2021 M1 MIT Yes Details →
3.1.2 19 Mar 2021 M1 MIT Yes Details →
3.1.1 18 Mar 2021 M1 MIT Yes Details →
3.1.0 13 Mar 2021 M1 MIT Yes Details →
3.0.6 11 Sep 2020 M1 MIT Yes Details →
3.0.5 14 Jun 2020 M1 MIT Yes Details →
3.0.4 08 Jun 2019 M1 MIT Yes Details →
3.0.3 25 May 2019 M1 MIT Yes Details →
3.0.2 27 Mar 2019 M1 MIT Yes Details →
3.0.1 02 Feb 2019 M1 MIT Yes Details →
3.0.0 09 Dec 2018 M1 MIT Yes Details →
2.2.3 27 Oct 2018 none MIT — Details →
2.2.2 29 Jun 2018 none MIT — Details →
2.2.1 02 Jun 2018 none MIT — Details →
2.2.0 10 May 2018 none MIT — Details →
2.1.1 26 Apr 2018 none MIT — Details →
2.1.0 09 Mar 2018 none MIT — Details →
2.0.0 28 Feb 2018 none MIT — Details →
1.1.1 10 Nov 2017 none MIT — Details →
1.1.0 02 Nov 2017 none MIT — Details →
1.0.0 29 Oct 2017 none MIT — Details →
0.0.8 01 Oct 2017 none MIT — Details →
0.0.7 30 Sep 2017 none MIT — Details →
0.0.6 30 Sep 2017 none MIT — Details →
0.0.5 27 Sep 2017 none MIT — Details →
0.0.4 27 Sep 2017 none MIT — Details →
0.0.3 27 Sep 2017 none MIT — Details →
0.0.2 23 Sep 2017 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 cross-fetch

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-1365: Incorrect Authorization in cross-fetch 6.1 medium 3.1.5 17 Apr 2022

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About cross-fetch

Is cross-fetch safe to use?

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

Vulert scores cross-fetch 76/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 cross-fetch affected?

No. 4.1.0, 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 cross-fetch should I use?

4.1.0 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 cross-fetch have?

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

0 vulnerabilities were recorded for cross-fetch in the last 12 months, and the oldest entry in this database dates to 17 Apr 2022. 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 cross-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 cross-fetch for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the cross-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.