Every CVE Search/ Get API key

CVE-2020-15168

File size limit bypass in node-fetch

2.6 LowFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
High
Privileges needed
Low
User interaction
Required

What an attacker can affect

Confidentiality
None
Integrity
None
Availability
Low

Exploit likelihood

1.69%Up 1.1 points since Apr 14, 2021
90%50%10%1%

What each source reports

CVE List Score used 2.6

File size limit bypass in node-fetch

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.

Record
CVE-2020-15168
CVSS 3.1
2.6 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Weakness
CWE-20, CWE-770
Updated
2026-11-02
EUVDEUVD-2020-1335 2.6

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.

Record
EUVD-2020-1335
CVSS 3.1
2.6 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Updated
2026-11-03
GitHub AdvisoriesGHSA-w7rc-rwvf-8q5r 2.6

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

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.
Record
GHSA-w7rc-rwvf-8q5r
CVSS 3.1
2.6 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Weakness
CWE-20, CWE-770
Updated
2026-11-02
NVD 2.6

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.

Record
CVE-2020-15168
CVSS 3.1
2.6 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
CVSS 3.1
5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CVSS 2.0
5.0 MediumAV:N/AC:L/Au:N/C:N/I:N/A:P
Weakness
CWE-20, CWE-770
Updated
2026-11-02
OSV 5.3

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.

Record
CVE-2020-15168
CVSS 3.1
5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Updated
2026-11-02
OSVDEBIAN-CVE-2020-15168 5.3

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.

Record
DEBIAN-CVE-2020-15168
CVSS 3.1
5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Updated
2026-11-02
Show 5 moreShow less
OSVGHSA-w7rc-rwvf-8q5r 2.6

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

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.
Record
GHSA-w7rc-rwvf-8q5r
CVSS 3.1
2.6 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Weakness
CWE-20, CWE-770
Updated
2026-11-02
OSVUBUNTU-CVE-2020-15168 2.6

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.

Record
UBUNTU-CVE-2020-15168
CVSS 3.1
2.6 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
CVSS 3.1
5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Updated
2026-11-02
OSVCLSA-2026-1792449835 No score

TuxCare security update for node-fetch (2 CVEs)

TuxCare rebuilt node-fetch to address 2 CVEs. Fixed in 2.6.0-tuxcare.1.

Record
CLSA-2026-1792449835
Updated
2026-11-02
OSVCLSA-2026-1793203551 No score

TuxCare security update for node-fetch (2 CVEs)

TuxCare rebuilt node-fetch to address 2 CVEs. Fixed in 2.1.2-tuxcare.1.

Record
CLSA-2026-1793203551
Updated
2026-11-02
OSVSUSE-SU-2020:3235-1 No score

Security update for SUSE Manager Server 4.1

This update fixes the following issues:

bind-formula:

  • Temporarily disable dnssec-validation as hotfix for bsc#1177790

grafana-formula:

  • Use variable for product name
  • Add HA/SAP dashboards
  • Add support for system groups in Client Systems dashboard

image-sync-formula:

  • Do not use .gz suffix for default initrd symlink
  • Keep the old symlink 'initrd.gz' for compatibility

prometheus-exporters-formula:

  • Fix empty directory values initialization
  • Add systemd collector as default for node_exporters since otherwise some SAP/HA grafana dashboards will be empty
  • Disable reverse proxy on default

prometheus-formula:

  • Disable Alertmanager clustering (bsc#1178145)
  • Use variable for product name

pxe-formula:

  • Change default to 'initrd' without .gz suffix

py26-compat-salt:

  • Properly validate eauth credentials and tokens on SSH calls made by Salt API (bsc#1178319, bsc#1178362, bsc#1178361, CVE-2020-25592, CVE-2020-17490, CVE-2020-16846)

python-susemanager-retail:

  • Use name 'initrd' without .gz suffix

salt-netapi-client:

saltboot-formula:

  • Allow setting terminal kernel parameters in saltboot formula

spacecmd:

  • Python3 fixes for errata in spacecmd (bsc#1169664)
  • Added support for i18n of user-facing strings
  • Python3 fix for sorted usage (bsc#1167907)

spacewalk-admin:

  • Show info message when applying schema upgrade

spacewalk-backend:

  • Prevent IntegrityError during mgr-inter-sync execution (bsc#1177235)

spacewalk-branding:

  • Enable to switch to multiple webUI theme

spacewalk-client-tools:

  • Remove RH references in Python/Ruby localization and use the product name instead

spacewalk-java:

  • Use correct eauth module and credentials for Salt SSH calls (bsc#1178319)
  • Remove expiration date from ics files (bsc#1177892)
  • Execute Salt SSH actions in parallel (bsc#1173199)
  • Enable to switch to multiple webUI theme
  • Fix action chain resuming when patches updating salt-minion don't cause service to be restarted (bsc#1144447)
  • Renaming autoinstall distro didn't change the name of the Cobbler distro (bsc#1175876)
  • Fix the links for downloading the binaries in the package details UI (bsc#1176603)
  • Allow nightly ISS sync to also cover custom channels
  • Fix: reinspecting a container image (bsc#1177092)
  • Add power management xmlrpc api
  • Remove hostname from /var/lib/salt/.ssh/known_hosts when deleting system (bsc#1176159)
  • Log exception trace on fatal Taskomatic startup error
  • Fix max password length check at user creation (bsc#1176765)
  • Notify about missing libvirt or hypervisor on virtual host
  • Redesign maintenance schedule systems table to use paginated data from server
  • Fix SP migration after dry run for cloned channels (bsc#1176307)
  • Filter not available optional channels out

spacewalk-search:

  • Change default maximum memory to 512 MB, preventing OutOfMemoryError

spacewalk-web:

  • Enable to switch to multiple webUI theme
  • Only refresh the virtual storage list when pool events are received
  • Drop node-fetch to fix CVE-2020-15168
  • Notify about missing libvirt or hypervisor on virtual host
  • Redesign maintenance schedule systems table to use paginated data from server

susemanager:

  • Create bootstrap repo should not flush by default (bsc#1175843)
  • Improve detection of base channels for products (bsc#1177478)
  • Add LTSS PIDs for SLE12SP1, SLE12SP2, SLE12SP3 and SLE12SP4 to the bootstrap definitions as some packages from LTSS are required (bsc#1177524)
  • Fix logrotate config
  • Add missing packages to ubuntu20.04 bootstrap data (bsc#1176629)

susemanager-build-keys:

  • Replace 'SuSE' user-facing references with 'SUSE'

susemanager-doc-indexes:

  • Documented zypper autorefresh feature in Upgrade Guide
  • Update SP Migration chapter in Client Configuration Guide
  • In Client Configuration and Upgrade Guide, add link to valid autoyast upgrade settings
  • Move client upgrade related sections from…
Record
SUSE-SU-2020:3235-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
node-fetch
npm
3.0.0-beta.1 to 3.0.0-beta.8
3.0.0-beta.9
node-fetch
npm
2.0.0 up to 2.6.1
2.6.1
node-fetch
TuxCare:npm
From an advisory covering 2 CVEs
2.6.0-tuxcare.0 up to 2.6.0-tuxcare.1, plus listed versions
2.6.0
2.6.0-tuxcare.1
node-fetch
TuxCare:npm
From an advisory covering 2 CVEs
2.1.2-tuxcare.0 up to 2.1.2-tuxcare.1, plus listed versions
2.1.2
2.1.2-tuxcare.1
node-fetch
Debian:12
before 2.6.1-2
2.6.1-2
node-fetch
Debian:13
before 2.6.1-2
2.6.1-2
node-fetch
Debian:14
before 2.6.1-2
2.6.1-2
node-fetch
npm
3.0.0-beta.1 up to 3.0.0-beta.9
3.0.0-beta.9
mgr-daemon
SUSE:Manager Proxy Module 4.1
From an advisory covering 4 CVEs
before 4.1.3-2.6.3
4.1.3-2.6.3
spacecmd
SUSE:Manager Proxy Module 4.1
From an advisory covering 4 CVEs
before 4.1.8-4.9.2
4.1.8-4.9.2
Show 30 moreShow less
Affected packages
PackageAffectedFixed
spacewalk-backend
SUSE:Manager Proxy Module 4.1
From an advisory covering 4 CVEs
before 4.1.16-4.11.5
4.1.16-4.11.5
spacewalk-client-tools
SUSE:Manager Proxy Module 4.1
From an advisory covering 4 CVEs
before 4.1.7-4.6.4
4.1.7-4.6.4
spacewalk-web
SUSE:Manager Proxy Module 4.1
From an advisory covering 4 CVEs
before 4.1.19-3.9.5
4.1.19-3.9.5
susemanager-build-keys
SUSE:Manager Proxy Module 4.1
From an advisory covering 4 CVEs
before 15.2.2-3.6.3
15.2.2-3.6.3
bind-formula
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.1.1603299886.60e4bcf-3.3.2
0.1.1603299886.60e4bcf-3.3.2
grafana-formula
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.3.0-3.3.2
0.3.0-3.3.2
image-sync-formula
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.1.1602150122.f08af0a-3.6.2
0.1.1602150122.f08af0a-3.6.2
prometheus-exporters-formula
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.8.0-3.16.2
0.8.0-3.16.2
prometheus-formula
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.3.0-3.3.1
0.3.0-3.3.1
pxe-formula
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.1.1602490840.4f32148-3.3.2
0.1.1602490840.4f32148-3.3.2
py26-compat-salt
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 2016.11.10-6.3.3
2016.11.10-6.3.3
python-susemanager-retail
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 1.0.1602150122.f08af0a-3.3.2
1.0.1602150122.f08af0a-3.3.2
salt-netapi-client
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.18.0-15.7.5
0.18.0-15.7.5
saltboot-formula
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 0.1.1602150122.f08af0a-3.6.2
0.1.1602150122.f08af0a-3.6.2
spacecmd
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.8-4.9.2
4.1.8-4.9.2
spacewalk-admin
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.7-3.6.3
4.1.7-3.6.3
spacewalk-backend
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.16-4.11.5
4.1.16-4.11.5
spacewalk-branding
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.11-3.9.6
4.1.11-3.9.6
spacewalk-client-tools
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.7-4.6.4
4.1.7-4.6.4
spacewalk-java
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.22-3.16.4
4.1.22-3.16.4
spacewalk-search
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.3-3.3.7
4.1.3-3.3.7
spacewalk-web
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.19-3.9.5
4.1.19-3.9.5
susemanager
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.21-3.11.6
4.1.21-3.11.6
susemanager-build-keys
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 15.2.2-3.6.3
15.2.2-3.6.3
susemanager-doc-indexes
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1-11.17.1
4.1-11.17.1
susemanager-docs_en
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1-11.17.1
4.1-11.17.1
susemanager-schema
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.15-3.11.2
4.1.15-3.11.2
susemanager-sls
SUSE:Manager Server Module 4.1
From an advisory covering 4 CVEs
before 4.1.17-3.13.6
4.1.17-3.13.6
node-fetch
Ubuntu:Pro:18.04:LTS
All versions, plus listed versions
1.7.3-11.7.3-1ubuntu0.1~esm1
None known
node-fetch
Ubuntu:20.04:LTS
All versions, plus listed versions
1.7.3-11.7.3-21.7.3-2ubuntu0.1
None known

History

History
RecordedChangedSources
affected, facts
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2020-15168 is a low vulnerability (CVSS 2.6) in Node-fetch, published September 10, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.69%, the 77th percentile. Fixed in node-fetch 3.0.0-beta.9.

References

Show 35 moreShow less
This page doesn't list everything

Left out here: the rest of 1 source description. The JSON record has them.

MoveEnter Open