CVE-2026-111756 · GHSA-q3jh-wrc6-jgq8
follow-redirects array-form headers bypass cross-origin credential stripping
- Risk score
- 67/100
- CVSS
- 8.2 v4.0
- Exploit chance (30 days)
- 0.5%
- Published
- 20 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- A vulnerability in follow-redirects allows an attacker to bypass cross-origin credential stripping, potentially leading to unauthorized access to sensitive data.
- Affected
- {'products': ['follow-redirects'], 'packages': ['npm'], 'versions': ['>= 1.16.0, < 1.16.1']}
- Fix
- Upgrade to version 1.16.1 or later
- Exploitation
- No known exploitation
Story map
At a glance
follow-redirects: Amber, patch this week. A vulnerability in follow-redirects allows an attacker to bypass cross-origin credential stripping, potentially leading to unauthorized access to sensitive data.
The flaws
- CVE-2026-111756: Follow-redirects array-form headers bypass cross-origin credential stripping (CVSS 8.2 · EPSS 0%)
- CVE-2026-111755: Follow-redirects sensitiveHeaders regex escaping can expose credential headers (CVSS 8.2 · EPSS 0%)
The fix
Upgrade follow-redirects: 1.16.1 or later on your release line
Who is exposed: {'products': ['follow-redirects'], 'packages': ['npm'], 'versions': ['>= 1.16.0, < 1.16.1']}
Where it stands
- No known exploitation
Connects to
- Same weakness: Information disclosure (CWE-200). 197 other warnings in 30 days
Why it is Amber
- CVSS 8.2 high
- Remotely exploitable without logging in
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| follow-redirects | npm | >= 1.16.0, < 1.16.1 | 1.16.1 |
References
- https://github.com/advisories/GHSA-q3jh-wrc6-jgq8
- https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-q3jh-wrc6-jgq8
- https://github.com/follow-redirects/follow-redirects/commit/9865ca45490e4d0f7b6944870318408344570aff
- https://github.com/follow-redirects/follow-redirects/releases/tag/v1.16.1
- https://github.com/advisories/GHSA-q3jh-wrc6-jgq8
Original description
follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From version 1.16.0 to before version 1.16.1, follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared sensitiveHeaders) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller's headers container with for...in and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node's underlying http.request, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, for...in yields the numeric indices "0", "1", "2" and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The sensitiveHeaders option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim's credential headers by responding with a cross-origin redirect. This issue has been patched in version 1.16.1.
Last activity 20 Oct 2026. Patch Forecast updates every hour.