{"id":"CVE-2020-15168","aliases":["GHSA-w7rc-rwvf-8q5r"],"url":"https://o3.security/vulnerability/CVE-2020-15168","summary":"The `size` option isn't honored after following a redirect in node-fetch","details":"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":"2020-09-10T19:15:13.490Z","modified":"2026-07-08T05:59:23.617885435Z","cvss":{"score":5.3,"severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"},"epss":{"score":0.01692,"percentile":0.75135,"asOf":"2026-08-16"},"cisaKev":null,"exploitsKnown":0,"affectedPackages":[{"ecosystem":"npm","name":"node-fetch","fixedVersion":"2.6.1"},{"ecosystem":"npm","name":"node-fetch","fixedVersion":"3.0.0-beta.9"}],"fix":null,"references":[{"type":"ADVISORY","url":"https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r"},{"type":"ADVISORY","url":"https://www.npmjs.com/package/node-fetch"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-07-08T05:59:23.617885435Z"}}