node-fetch vulnerabilities

A light-weight module that brings Fetch API to node.js

Registry
npm
Latest
3.3.2
License
MIT

3 known advisories

The latest version, 3.3.2, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install node-fetch@3.3.2

Security advisories for node-fetch

  • MediumGHSA-vp56-6g26-68272 Aug 2022

    node-fetch Inefficient Regular Expression Complexity

    Affected
    >=3.0.0 <3.2.10
    Fixed in
    3.2.10
  • HighGHSA-r683-j2x4-v87g21 Jan 2022

    node-fetch forwards secure headers to untrusted sites

    Affected
    >=3.0.0 <3.1.1 · <2.6.7
    Fixed in
    2.6.7, 3.1.1
  • LowGHSA-w7rc-rwvf-8q5r10 Sept 2020

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

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

Which of your client projects still run an old node-fetch?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.