CVE-2026-40895: follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Targets
Summary 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:469-476). Any custom authentication header (e.g., X-API-Key, X-Auth-Token, Api-Key, Token) is forwarded verbatim to the redirect target.
Published Apr 14, 2026 · Updated Nov 2, 2026
Affected packages
follow-redirects
- Ecosystem
- npm
- Affected
- <= 1.15.11
- Fixed in
- 1.16.0
- Check
npm ls follow-redirects
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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:469-476). Any custom authentication header (e.g., X-API-Key, X-Auth-Token, Api-Key, Token) is forwarded verbatim to the redirect target.
Since follow-redirects is the redirect-handling dependency for axios (105K+ stars), this vulnerability affects the entire axios ecosystem.
Affected Code
index.js, lines 469-476:
if (redirectUrl.protocol !== currentUrlParts.protocol &&
redirectUrl.protocol !== "https:" ||
redirectUrl.host !== currentHost &&
!isSubdomain(redirectUrl.host, currentHost)) {
removeMatchingHeaders(/^(?:(?:proxy-)?authorization|cookie)$/i, this._options.headers);
}The regex only matches authorization, proxy-authorization, and cookie. Custom headers like X-API-Key are not matched.
Attack Scenario
- App uses axios with custom auth header:
headers: { 'X-API-Key': 'sk-live-secret123' } - Server returns
302 Location: https://evil.com/steal - follow-redirects sends
X-API-Key: sk-live-secret123toevil.com - Attacker captures the API key
Impact
Any custom auth header set via axios leaks on cross-domain redirect. Extremely common pattern. Affects all axios users in Node.js.
Suggested Fix
Add a sensitiveHeaders option that users can extend, or strip ALL non-standard headers on cross-domain redirect.
Disclosure
Source code review, manually verified. Found 2026-03-20.
Credited to Den-Sec.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-116689
follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects
high5.9Oct 30, 2026CVE-2026-111755
follow-redirects sensitiveHeaders regex escaping can expose credential headers
high8.2Oct 20, 2026CVE-2026-111756
follow-redirects array-form headers bypass cross-origin credential stripping
high8.2Oct 20, 2026CVE-2024-28849
follow-redirects' Proxy-Authorization header kept across hosts
medium6.5Mar 14, 2024CVE-2023-26159
Follow Redirects improperly handles URLs in the url.parse() function
medium6.1Jan 2, 2024
