← Back

Node Fetch Project

node-fetch_project

3 CVEs • 1 product

Products (1)

Click to collapse
Toggle
Node Fetch
node-fetch

CVEs (3)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Node Fetch Project
1Node Fetch
Feb 25, 2026
Aug 1, 2022
N/A· v4
5.9 MEDIUM· v3
N/A· v2
Inefficient Regular Expression Complexity in GitHub repository node-fetch/node-fetch prior to 3.2.10.
3Debian
Node Fetch ProjectSiemens
3Debian Linux
Node FetchSinec Ins
Nov 21, 2024
Jan 16, 2022
N/A· v4
6.1 MEDIUM· v3
5.8 MEDIUM· v2
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
1Node Fetch Project
1Node Fetch
Nov 21, 2024
Sep 10, 2020
N/A· v4
5.3 MEDIUM· v3
5.0 MEDIUM· v2
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process wou...Show more
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.Show less