Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111756 Overview
CVE-2026-111756 is an information disclosure vulnerability [CWE-200] in the follow-redirects Node.js HTTP and HTTPS client wrapper. Versions 1.16.0 up to (but not including) 1.16.1 fail to strip sensitive credential headers when applications supply headers in array form and the client follows a cross-origin or protocol-downgrading redirect. Affected applications forward Authorization, Cookie, and Proxy-Authorization headers verbatim to attacker-controlled destinations without any error or warning. The flaw also defeats the sensitiveHeaders mitigation introduced for CVE-2026-40895, because both features share the same filtering helper.
Critical Impact
Any remote server a vulnerable Node.js application contacts can harvest the victim's credentials by responding with a cross-origin HTTP redirect.
Affected Products
- follow-redirects npm package version 1.16.0
- follow-redirects versions prior to 1.16.1
- Node.js applications passing headers as alternating name/value arrays to http.request through follow-redirects
Discovery Timeline
- 2026-10-20 - CVE-2026-111756 published to the National Vulnerability Database
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-111756
Vulnerability Analysis
The follow-redirects library acts as a drop-in replacement for Node's http.request and https.request. When a redirect crosses origins or downgrades the protocol, the library attempts to remove headers listed in a filter that includes Authorization, Proxy-Authorization, Cookie, and any entries declared in sensitiveHeaders.
The removal routine iterates the caller's headers container with a for...in loop and compares each key against the filter. This logic assumes options.headers is a plain object keyed by header names. Node's underlying request API also accepts headers as an alternating array of names and values, in which case for...in yields numeric indices ("0", "1", "2") that never match a header-name filter. The filter runs, finds nothing to remove, and the redirect proceeds with every credential header intact.
An attacker only needs to control any endpoint the victim application contacts. Returning a 302 redirect to an attacker-controlled host causes the vulnerable client to forward credentials to that host silently. See the GitHub Security Advisory GHSA-q3jh-wrc6-jgq8 for the full write-up.
Root Cause
The sensitive-header stripping function fails to normalize array-form header input before enumeration. Because for...in over an array yields indices rather than header names, the filter never matches, and the mitigation added for CVE-2026-40895 inherits the same defect.
Attack Vector
Exploitation is unauthenticated and remote. Any HTTP server the victim contacts (including compromised third-party APIs, redirect services, or attacker-controlled callbacks) can respond with a cross-origin redirect. The vulnerable client re-sends the original Authorization, Cookie, and Proxy-Authorization headers to the attacker-controlled destination.
if (!options.headers) {
options.headers = {};
}
+ // Convert [header1, value1, header2, value2, …] to object
+ else if (Array.isArray(options.headers)) {
+ var headerList = options.headers;
+ options.headers = {};
+ for (var i = 0; i < headerList.length; i += 2) {
+ options.headers[headerList[i]] = headerList[i + 1];
+ }
+ }
+ // Ensure sensitive headers are always present
if (!isArray(options.sensitiveHeaders)) {
options.sensitiveHeaders = [];
}
Source: follow-redirects commit 9865ca4. The patch normalizes array-form headers into a plain object before the sensitive-header filter runs, restoring the intended stripping behavior.
Detection Methods for CVE-2026-111756
Indicators of Compromise
- Outbound HTTP requests from Node.js services carrying Authorization, Cookie, or Proxy-Authorization headers to hosts outside the application's expected API inventory.
- Redirect chains (3xx responses) from known-good upstream services terminating at previously unseen or low-reputation destinations.
- Application logs showing follow-redirects cross-origin redirects immediately preceded by requests with array-form header arguments.
Detection Strategies
- Inventory Node.js dependencies using npm ls follow-redirects and flag any resolved version equal to 1.16.0.
- Perform static code review for call sites passing an Array to the headers option of http.request, https.request, axios, or wrappers that embed follow-redirects.
- Enable egress TLS inspection or proxy logging to detect credential headers being transmitted to unapproved hostnames.
Monitoring Recommendations
- Alert on new outbound destinations contacted by Node.js workloads shortly after a 3xx response from a trusted upstream.
- Track Software Bill of Materials (SBOM) changes to catch transitive upgrades to follow-redirects 1.16.0.
- Monitor authentication backends for anomalous reuse of bearer tokens or session cookies from unexpected source IPs.
How to Mitigate CVE-2026-111756
Immediate Actions Required
- Upgrade follow-redirects to version 1.16.1 or later across all direct and transitive dependencies.
- Rotate any bearer tokens, API keys, session cookies, and proxy credentials that may have transited vulnerable clients.
- Audit outbound request code to replace array-form headers with plain object headers until all consumers are patched.
Patch Information
The fix is available in the follow-redirects v1.16.1 release. Commit 9865ca4 converts array-form header input into a plain object before the sensitive-header filter executes, restoring correct stripping on cross-origin and protocol-downgrade redirects.
Workarounds
- Convert all options.headers arguments from arrays to plain objects before invoking any follow-redirects-backed client.
- Disable automatic redirect following (maxRedirects: 0) for requests that carry authentication headers, and handle redirects explicitly.
- Route outbound traffic through an egress proxy that strips credential headers on cross-origin redirects.
# Pin or upgrade follow-redirects to the patched release
npm install follow-redirects@^1.16.1
# Verify no transitive dependency resolves to 1.16.0
npm ls follow-redirects
# Audit the project for known advisories
npm audit --production
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

