---
title: "GHSA-r4q5-vmmm-2653: follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Targets"
description: "Moderate severity. follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Targets. Affects follow-redirects; fixed in 1.16.0."
url: https://inlinr.com/advisories/GHSA-r4q5-vmmm-2653
lang: en
---

[Packages](https://inlinr.com/packages) / [follow-redirects](https://inlinr.com/packages/follow-redirects) / [Security](https://inlinr.com/packages/follow-redirects/security)

Moderate Vulnerability GHSA-r4q5-vmmm-2653 CVE-2026-40895 Published 14 Apr 2026

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

Your version 

Affected releases · [follow-redirects](https://inlinr.com/packages/follow-redirects)

- 1.x 1.0.0 – 1.15.11 Fixed in 1.16.0
- 0.3.x and older 0.0.1 – 0.3.0 No fix, no longer updated

On 1.x, the newest line:

```
npm install follow-redirects@1.16.0
```

Every release on a timeline

1.x 

1. Affected

1.0.0 – 1.15.11  
60 releases
2. Fixed

1.16.0 – 1.16.3  
4 releases, latest

0.x 

1. Affected

0.0.1 – 0.3.0  
10 releases

74 stable releases of follow-redirects, oldest to newest, one row per major.

## What happens

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

1. App uses axios with custom auth header: `headers: { 'X-API-Key': 'sk-live-secret123' }`
2. Server returns `302 Location: https://evil.com/steal`
3. follow-redirects sends `X-API-Key: sk-live-secret123` to `evil.com`
4. 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.

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: low
- **Integrity**: none
- **Availability**: none

CVSS:4.0/​AV:N/​AC:L/​AT:N/​PR:N/​UI:N/​VC:L/​VI:N/​VA:N/​SC:N/​SI:N/​SA:N

## References

- [Reference](https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-r4q5-vmmm-2653 "https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-r4q5-vmmm-2653")  
github.com/follow-redirects/follow-redirects/se…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-40895 "https://nvd.nist.gov/vuln/detail/CVE-2026-40895")  
nvd.nist.gov/vuln/detail/CVE-2026-40895
- [Fix commit](https://github.com/follow-redirects/follow-redirects/commit/844c4d302ac963d29bdb5dc1754ec7df3d70d7f9 "https://github.com/follow-redirects/follow-redirects/commit/844c4d302ac963d29bdb5dc1754ec7df3d70d7f9")  
844c4d3
- [Package](https://github.com/follow-redirects/follow-redirects "https://github.com/follow-redirects/follow-redirects")  
github.com/follow-redirects/follow-redirects

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
