Vulnerability Database · npm · node-fetch · Version
node-fetch 2.1.0
2.1.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.3.2.
Critical 0 High 0 Medium 0 Low 1 Unrated 0
-
Released 05 Mar 2018
Licence MIT
Also known from other sources 2
Newer releases 96
Database updated 22/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
node-fetch 2.1.0 vulnerabilities
1 vulnerability cover node-fetch 2.1.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-15168: Node-fetch size option not honored after redirect | 2.6 low | 2.6.1 | 10 Sep 2020 |
Looking for another version, or everything Vulert holds for node-fetch?
Questions
About node-fetch 2.1.0
Is node-fetch 2.1.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover node-fetch 2.1.0: 0 critical, 0 high, 0 medium and 1 low. The upgrade Vulert recommends is 3.3.2, and each entry above names the fixed version to move to.
Which version of node-fetch should I use instead of 2.1.0?
3.3.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.1.0 the latest release of node-fetch?
No. 2.1.0 was published 05 Mar 2018, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.