follow-redirects
1.16.3 · 8 Nov 2026MIT149.9M / weekRepositorynpmAtom feed
Upgrading follow-redirects From 1.13.2 to 1.16.0
24 releases in betweennotes for 0
Reading releases, release notes and advisories…
Other targets from 1.13.2Newest 1.x, Latest1.16.3
- ?
- changes to make
- 5
- advisories fixed
- ?
- new
- ?
- fixes
Counted from 0 of 24 release notes. Advisories are counted from the advisory database, in full.
Security
3 advisories still affect 1.16.0
- follow-redirects sensitiveHeaders regex escaping can expose credential headershigh · GHSA-8r9p-f939-6h3c
- follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirectshigh · GHSA-mrwp-f3q8-3g9p
- follow-redirects array-form headers bypass cross-origin credential strippinghigh · GHSA-q3jh-wrc6-jgq8
Upgrading to 1.16.2 clears them.
Fixes 5 advisories affecting 1.13.2
- Exposure of sensitive information in follow-redirectshigh · GHSA-74fj-2j2h-c42q
- follow-redirects' Proxy-Authorization header kept across hostsmoderate · GHSA-cxjh-pqwp-8mfp
- Follow Redirects improperly handles URLs in the url.parse() functionmoderate · GHSA-jchw-25xp-jwwc
- Exposure of Sensitive Information to an Unauthorized Actor in follow-redirectsmoderate · GHSA-pw2r-vq6v-hr8c
- follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Targetsmoderate · GHSA-r4q5-vmmm-2653
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.