Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.6amended

The size option isn't honored after following a redirect in node-fetch

CVE-2020-15168GHSA-w7rc-rwvf-8q5r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (node-fetch 3.0.0-beta.9, 2.6.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm node-fetch

    Affected
    >= 3.0.0-beta.1, <= 3.0.0-beta.8>= 2.0.0, < 2.6.1
    Fixed in
    3.0.0-beta.9, 2.6.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.6 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
EPSS
  • CVE-2020-15168: 1.69% estimated exploitation activity in the next 30 days; percentile 77.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Node Fetch 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. Patches We released patched versions for both stable and beta channels: - For v2: 2.6.1 - For v3: 3.0.0-beta.9 Workarounds None, it is strongly recommended to update as soon as possible. For more information If you have any questions or comments about this advisory: Open an issue in node-fetch Contact one of the core maintainers.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-w7rc-rwvf-8q5r

  2. Revision 1 · created ·

    Published from osv record GHSA-w7rc-rwvf-8q5r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-15168

Advisory: The `size` option isn't honored after following a redirect in node-fetch
IDs: CVE-2020-15168, GHSA-w7rc-rwvf-8q5r
Record: https://patchnext.com/advisories/cve-2020-15168 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node-fetch 3.0.0-beta.9, 2.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm node-fetch: affected >= 3.0.0-beta.1, <= 3.0.0-beta.8; >= 2.0.0, < 2.6.1; fixed in 3.0.0-beta.9, 2.6.1

## Suggested inspection (read-only)
- `npm ls node-fetch --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node-fetch.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w7rc-rwvf-8q5r (OSV record GHSA-w7rc-rwvf-8q5r lists affected ranges: npm node-fetch >=2.0.0 =3.0.0-beta.1 <3.0.0-beta.9 (fixed))
- Verified: https://github.com/advisories/GHSA-w7rc-rwvf-8q5r (GitHub-reviewed advisory GHSA-w7rc-rwvf-8q5r lists affected ranges: npm node-fetch >=3.0.0-beta.1 =2.0.0 <2.6.1)

Commands are suggestions: review each one before running it.

Loading voting…