GHSA-w7rc-rwvf-8q5r The `size` option isn't honored after following a redirect in node-fetch

• npm node-fetch: >= 2.0.0, < 2.6.1 → fixed in 2.6.1 • npm node-fetch: >= 3.0.0-beta.1, < 3.0.0-beta.9 → fixed in 3.0.0-beta.9

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.