VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

follow-redirects: vulnerability history, versions and safety

follow-redirects is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 71 releases, from Jan 2022 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H3 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 20 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all follow-redirects vulnerabilities

Vulert verdict on follow-redirects 1.16.1 i

Updated on 22 Oct 2026

Good news: 1.16.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 76/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on 1.16.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.16.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.16.1 — unaffected i
  • Vulnerabilities on record 7 over 4 years · 3 in the last year i
  • Latest disclosure 20 Oct 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 366,138 packages i
  • Stars 580 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for follow-redirects, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.16.1 01 Oct 2026 none MIT — Details →
1.16.0 13 Apr 2026 H2 MIT Yes Details →
1.15.11 31 Jul 2025 M1 MIT Yes Details →
1.15.10 31 Jul 2025 M1 MIT Yes Details →
1.15.9 06 Sep 2024 M1 MIT Yes Details →
1.15.8 03 Sep 2024 M1 MIT Yes Details →
1.15.7 03 Sep 2024 M1 MIT Yes Details →
1.15.6 14 Mar 2024 M1 MIT Yes Details →
1.15.5 12 Jan 2024 M2 MIT Yes Details →
1.15.4 30 Dec 2023 M2 MIT Yes Details →
1.15.3 19 Sep 2023 M3 MIT Yes Details →
1.15.2 13 Sep 2022 M3 MIT Yes Details →
1.15.1 26 May 2022 M3 MIT Yes Details →
1.15.0 03 May 2022 M3 MIT Yes Details →
1.14.9 18 Feb 2022 M3 MIT Yes Details →
1.14.8 08 Feb 2022 M3 MIT Yes Details →
1.14.7 10 Jan 2022 M4 MIT Yes Details →
1.14.6 08 Dec 2021 H1 M4 MIT Yes Details →
1.14.5 30 Oct 2021 H1 M4 MIT Yes Details →
1.14.4 14 Sep 2021 H1 M4 MIT Yes Details →
1.14.3 02 Sep 2021 H1 M4 MIT Yes Details →
1.14.2 18 Aug 2021 H1 M4 MIT Yes Details →
1.14.1 09 May 2021 H1 M4 MIT Yes Details →
1.14.0 25 Apr 2021 H1 M4 MIT Yes Details →
1.13.3 27 Feb 2021 H1 M4 MIT Yes Details →
1.13.2 25 Jan 2021 H1 M4 MIT Yes Details →
1.13.1 13 Dec 2020 H1 M4 MIT Yes Details →
1.13.0 10 Aug 2020 H1 M4 MIT Yes Details →
1.12.1 18 Jun 2020 H1 M4 MIT Yes Details →
1.12.0 16 Jun 2020 H1 M4 MIT Yes Details →
1.11.0 29 Mar 2020 H1 M4 MIT Yes Details →
1.10.0 26 Jan 2020 H1 M4 MIT Yes Details →
1.9.1 25 Jan 2020 H1 M4 MIT Yes Details →
1.9.0 06 Sep 2019 H1 M4 MIT Yes Details →
1.8.1 27 Aug 2019 H1 M4 MIT Yes Details →
1.8.0 27 Aug 2019 H1 M4 MIT Yes Details →
1.7.0 13 Feb 2019 H1 M4 MIT Yes Details →
1.6.1 03 Jan 2019 H1 M4 MIT Yes Details →
1.6.0 25 Dec 2018 H1 M4 MIT Yes Details →
1.5.10 19 Nov 2018 H1 M4 MIT Yes Details →
1.5.9 09 Oct 2018 H1 M4 MIT Yes Details →
1.5.8 11 Sep 2018 H1 M4 MIT Yes Details →
1.5.7 22 Aug 2018 H1 M4 MIT Yes Details →
1.5.6 21 Aug 2018 H1 M4 MIT Yes Details →
1.5.5 13 Aug 2018 H1 M4 MIT Yes Details →
1.5.4 13 Aug 2018 H1 M4 MIT Yes Details →
1.5.3 13 Aug 2018 H1 M4 MIT Yes Details →
1.5.2 01 Aug 2018 H1 M4 MIT Yes Details →
1.5.1 05 Jul 2018 H1 M4 MIT Yes Details →
1.5.0 19 May 2018 H1 M4 MIT Yes Details →
1.4.1 24 Jan 2018 H1 M4 MIT Yes Details →
1.4.0 21 Jan 2018 H1 M4 MIT Yes Details →
1.3.0 05 Jan 2018 H1 M4 MIT Yes Details →
1.2.6 22 Nov 2017 H1 M4 MIT Yes Details →
1.2.5 05 Oct 2017 H1 M4 MIT Yes Details →
1.2.4 21 Jun 2017 H1 M4 MIT Yes Details →
1.2.3 10 Mar 2017 H1 M4 MIT Yes Details →
1.2.2 09 Mar 2017 H1 M4 MIT Yes Details →
1.2.1 18 Dec 2016 H1 M4 MIT Yes Details →
1.2.0 07 Dec 2016 H1 M4 MIT Yes Details →
1.1.0 06 Nov 2016 H1 M4 MIT Yes Details →
1.0.0 23 Oct 2016 H1 M4 MIT Yes Details →
0.3.0 20 Oct 2016 H1 M4 MIT Yes Details →
0.2.0 06 Jun 2016 H1 M4 MIT Yes Details →
0.1.0 10 Apr 2016 H1 M4 MIT Yes Details →
0.0.7 10 Sep 2015 H1 M4 MIT Yes Details →
0.0.6 04 Jul 2015 H1 M4 MIT Yes Details →
0.0.5 01 Jul 2015 H1 M4 MIT Yes Details →
0.0.4 01 Jul 2015 H1 M4 MIT Yes Details →
0.0.3 29 Nov 2012 H1 M4 non-standard Yes Details →
0.0.2 21 Nov 2012 H1 M4 non-standard Yes Details →
0.0.1 15 Nov 2012 H1 M4 non-standard Yes Details →

All 72 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2024 2
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for follow-redirects

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-111755: follow-redirects Credential Header Exposure via Regex Escaping 8.2 high 1.16.1 20 Oct 2026
CVE-2026-111756: follow-redirects Package Vulnerability Leading to Credential Leakage 8.2 high 1.16.1 20 Oct 2026
CVE-2022-0155: Exposure of sensitive information in follow-redirects 8.0 high 1.14.7 12 Jan 2022
Custom Authentication Header Leakage in follow-redirects Package 6.9 medium 1.16.0 14 Apr 2026
CVE-2024-28849: Vulnerability in follow-redirects package 6.5 medium 1.15.6 14 Mar 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About follow-redirects

Is follow-redirects safe to use?

Vulert records 7 vulnerabilities for follow-redirects in npm: 0 critical, 3 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is follow-redirects's Vulert package health score?

Vulert scores follow-redirects 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of follow-redirects affected?

No. 1.16.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of follow-redirects should I use?

1.16.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does follow-redirects have?

7 vulnerabilities are recorded for follow-redirects in the npm ecosystem: 0 critical, 3 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new follow-redirects vulnerabilities disclosed?

3 vulnerabilities were recorded for follow-redirects in the last 12 months, and the oldest entry in this database dates to 12 Jan 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of follow-redirects are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor follow-redirects for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the follow-redirects version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.