Is follow-redirects 1.2 vulnerable?

npm · 7 releases from 1.2.0 to 1.2.6 · latest follow-redirects is 1.16.2 · checked 2 Nov 2026

Yes: 5 known advisories

Yes. follow-redirects 1.2.6, the last 1.2 release, is affected by 5 known security advisories (1 high, 4 medium), including CVE-2022-0155, CVE-2026-40895, CVE-2024-28849. Upgrade to 1.16.0 or later to fix all of them.

Upgrade with:npm install follow-redirects@1.16.0

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting follow-redirects 1.2.6

  • MediumCVE-2026-40895GHSA-r4q5-vmmm-265314 Apr 2026

    follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Targets

    Affected
    <1.16.0
    Fixed in
    1.16.0
  • MediumCVE-2024-28849GHSA-cxjh-pqwp-8mfp14 Mar 2024

    follow-redirects' Proxy-Authorization header kept across hosts

    Affected
    <1.15.6
    Fixed in
    1.15.6
  • MediumCVE-2023-26159GHSA-jchw-25xp-jwwc2 Jan 2024

    Follow Redirects improperly handles URLs in the url.parse() function

    Affected
    <1.15.4
    Fixed in
    1.15.4
  • MediumCVE-2022-0536GHSA-pw2r-vq6v-hr8c10 Feb 2022

    Exposure of Sensitive Information to an Unauthorized Actor in follow-redirects

    Affected
    <1.14.8
    Fixed in
    1.14.8
  • HighCVE-2022-0155GHSA-74fj-2j2h-c42q12 Jan 2022

    Exposure of sensitive information in follow-redirects

    Affected
    <1.14.7
    Fixed in
    1.14.7

Which of your client projects are still on follow-redirects 1.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact follow-redirects version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other follow-redirects versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.