NVD / CVE Program· CNA GitHub_M

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

MediumCVSS 5.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 77.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: node-fetch (Debian:12) 2.6.1-2; node-fetch (npm) 2.6.1, 3.0.0-beta.9; mgr-daemon (SUSE:Manager Proxy Module 4.1) 4.1.3-2.6.3.
Severity is disputed: the assigning authority (CNA) scores it 2.6, NVD 5.3.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to node-fetch (Debian:12) 2.6.1-2; node-fetch (npm) 2.6.1, 3.0.0-beta.9; mgr-daemon (SUSE:Manager Proxy Module 4.1) 4.1.3-2.6.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Sep 10, 2020
Updated: Jun 16, 2026
EPSS: 1.6% · 77th percentile
CWE: CWE-20

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 1.6%

CNA vs NVD score

NVD: 5.3
CNA · GitHub_M: 2.6; 2.7 point gap

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
node-fetch project	node-fetch	cpe:2.3:a:node-fetch_project:node-fetch

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

node-fetch node-fetch
- <2.6.1, >3.0.0-beta.1, <3.0.0-beta.9affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

node-fetch project node-fetchbefore 2.6.1
node-fetch project node-fetch3.0.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	node-fetch	before 2.6.1-2	2.6.1-2
npm	node-fetch	from 2.0.0 · before 2.6.1	2.6.1
npm	node-fetch	from 3.0.0-beta.1 · before 3.0.0-beta.9	3.0.0-beta.9
SUSE:Manager Proxy Module 4.1	mgr-daemon	before 4.1.3-2.6.3	4.1.3-2.6.3
SUSE:Manager Proxy Module 4.1	spacecmd	before 4.1.8-4.9.2	4.1.8-4.9.2
SUSE:Manager Proxy Module 4.1	spacewalk-backend	before 4.1.16-4.11.5	4.1.16-4.11.5
SUSE:Manager Proxy Module 4.1	spacewalk-client-tools	before 4.1.7-4.6.4	4.1.7-4.6.4
SUSE:Manager Proxy Module 4.1	spacewalk-web	before 4.1.19-3.9.5	4.1.19-3.9.5
SUSE:Manager Proxy Module 4.1	susemanager-build-keys	before 15.2.2-3.6.3	15.2.2-3.6.3
SUSE:Manager Server Module 4.1	bind-formula	before 0.1.1603299886.60e4bcf-3.3.2	0.1.1603299886.60e4bcf-3.3.2
SUSE:Manager Server Module 4.1	grafana-formula	before 0.3.0-3.3.2	0.3.0-3.3.2
SUSE:Manager Server Module 4.1	image-sync-formula	before 0.1.1602150122.f08af0a-3.6.2	0.1.1602150122.f08af0a-3.6.2
SUSE:Manager Server Module 4.1	prometheus-exporters-formula	before 0.8.0-3.16.2	0.8.0-3.16.2
SUSE:Manager Server Module 4.1	prometheus-formula	before 0.3.0-3.3.1	0.3.0-3.3.1
SUSE:Manager Server Module 4.1	pxe-formula	before 0.1.1602490840.4f32148-3.3.2	0.1.1602490840.4f32148-3.3.2
SUSE:Manager Server Module 4.1	py26-compat-salt	before 2016.11.10-6.3.3	2016.11.10-6.3.3
SUSE:Manager Server Module 4.1	python-susemanager-retail	before 1.0.1602150122.f08af0a-3.3.2	1.0.1602150122.f08af0a-3.3.2
SUSE:Manager Server Module 4.1	salt-netapi-client	before 0.18.0-15.7.5	0.18.0-15.7.5
SUSE:Manager Server Module 4.1	saltboot-formula	before 0.1.1602150122.f08af0a-3.6.2	0.1.1602150122.f08af0a-3.6.2
SUSE:Manager Server Module 4.1	spacewalk-admin	before 4.1.7-3.6.3	4.1.7-3.6.3
SUSE:Manager Server Module 4.1	spacewalk-branding	before 4.1.11-3.9.6	4.1.11-3.9.6
SUSE:Manager Server Module 4.1	spacewalk-java	before 4.1.22-3.16.4	4.1.22-3.16.4
SUSE:Manager Server Module 4.1	spacewalk-search	before 4.1.3-3.3.7	4.1.3-3.3.7
SUSE:Manager Server Module 4.1	susemanager	before 4.1.21-3.11.6	4.1.21-3.11.6

Same product

node-fetch project: all records

Other highest-scoring records for the same primary product.

CVE-2022-0235Exposure of Sensitive Information to an Unauthorized Actor in node-fetch/node-fetch
25Monitor
CVE-2022-2596Inefficient Regular Expression Complexity in node-fetch/node-fetch
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:node-fetch	2.6.1-2 · Debian:12	Package registry (OSV)
npm:node-fetch	2.6.1	Package registry (OSV)
npm:node-fetch	3.0.0-beta.9	Package registry (OSV)
suse:bind-formula	0.1.1603299886.60e4bcf-3.3.2 · SUSE:Manager Server Module 4.1	Package registry (OSV)
suse:grafana-formula	0.3.0-3.3.2 · SUSE:Manager Server Module 4.1	Package registry (OSV)
suse:image-sync-formula	0.1.1602150122.f08af0a-3.6.2 · SUSE:Manager Server Module 4.1	Package registry (OSV)
suse:mgr-daemon	4.1.3-2.6.3 · SUSE:Manager Proxy Module 4.1	Package registry (OSV)
suse:prometheus-exporters-formula	0.8.0-3.16.2 · SUSE:Manager Server Module 4.1	Package registry (OSV)
suse:prometheus-formula	0.3.0-3.3.1 · SUSE:Manager Server Module 4.1	Package registry (OSV)
suse:pxe-formula	0.1.1602490840.4f32148-3.3.2 · SUSE:Manager Server Module 4.1	Package registry (OSV)
suse:spacecmd	4.1.8-4.9.2 · SUSE:Manager Proxy Module 4.1	Package registry (OSV)
suse:spacewalk-backend	4.1.16-4.11.5 · SUSE:Manager Proxy Module 4.1	Package registry (OSV)
suse:spacewalk-client-tools	4.1.7-4.6.4 · SUSE:Manager Proxy Module 4.1	Package registry (OSV)
suse:spacewalk-web	4.1.19-3.9.5 · SUSE:Manager Proxy Module 4.1	Package registry (OSV)
suse:susemanager-build-keys	15.2.2-3.6.3 · SUSE:Manager Proxy Module 4.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.