Follow Redirects Project Follow Redirects vulnerabilities

4 vulnerabilities

Known vulnerabilities in Follow Redirects Project Follow Redirects, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

5.9CVE-2022-0536chainguardarangodb-3.11+5
EPSS score
1.27%
Improper Removal of Sensitive Information Before Storage or Transfer in NPM follow-redirects prior to 1.14.8.8CVE-2022-0155chainguardarangodb-3.11+6
EPSS score
2.43%
follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor6.5CVE-2024-28849chainguardarangodb-3.11+30
EPSS score
1.04%
follow-redirects is an open source, drop-in replacement for Node's `http` and `https` modules that automatically follows redirects. In affected versions follow-redirects only clears authorization header during cross-domain redirect, but keep the proxy-authentication header which contains credentials too. This vulnerability may lead to credentials leak, but has been addressed in version 1.15.6. Users are advised to upgrade. There are no known workarounds for this vulnerability.7.5CVE-2026-40895debiannode-follow-redirects+4
EPSS score
0.82%
follow-redirects is an open source, drop-in replacement for Node's `http` and `https` modules that automatically follows redirects. Prior to 1.16.0, when an HTTP request follows a cross-domain redirect (301/302/307/308), follow-redirects only strips authorization, proxy-authorization, and cookie headers (matched by regex at index.js). Any custom authentication header (e.g., X-API-Key, X-Auth-Token, Api-Key, Token) is forwarded verbatim to the redirect target. This vulnerability is fixed in 1.16.0.