node-follow-redirects — security advisory
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
- Products
- node-follow-redirects
- Affected versions
- 1.15.11+~1.14.4-1, 1.15.11+~1.14.4-2, 1.15.2+~1.14.1-1, 1.15.3+~1.14.2-1, 1.15.6+~1.14.4-1, 1.15.6+~1.14.4-2, 1.15.9+~1.14.4-1, 1.16.0+~1.14.4-1, 1.16.0+~1.14.4-2, 1.16.1+~1.14.4-1
- Fixed versions
- 1.16.1+~1.14.4-1
- CVEs
- CVE-2026-111756
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 18:47 UTC · Revision 1
Source evidence
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
osv:DEBIAN-CVE-2026-111756
node-follow-redirects
Fixed versions: Not specified
node-follow-redirects
Fixed versions: Not specified
node-follow-redirects
Fixed versions: 1.16.1+~1.14.4-1
Complete source record
{
"id": "a748bbac9300f04875765552385f3847fbcd1f65c3652a52f3a28fcc46e57397",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-111756",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-111756",
"summary": "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",
"evidence": "osv:DEBIAN-CVE-2026-111756",
"products": [
{
"name": {
"value": "node-follow-redirects",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "1.15.11+~1.14.4-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.15.11+~1.14.4-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.15.2+~1.14.1-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.15.3+~1.14.2-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.15.6+~1.14.4-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.15.6+~1.14.4-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.15.9+~1.14.4-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.16.0+~1.14.4-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.16.0+~1.14.4-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.16.1+~1.14.4-1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "node-follow-redirects",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "1.15.11+~1.14.4-1",
"evidence": "/affected/1/versions"
},
{
"value": "1.15.11+~1.14.4-2",
"evidence": "/affected/1/versions"
},
{
"value": "1.15.9+~1.14.4-1",
"evidence": "/affected/1/versions"
},
{
"value": "1.16.0+~1.14.4-1",
"evidence": "/affected/1/versions"
},
{
"value": "1.16.0+~1.14.4-2",
"evidence": "/affected/1/versions"
},
{
"value": "1.16.1+~1.14.4-1",
"evidence": "/affected/1/versions"
}
]
},
{
"name": {
"value": "node-follow-redirects",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.16.1+~1.14.4-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": [
{
"value": "1.15.11+~1.14.4-1",
"evidence": "/affected/2/versions"
},
{
"value": "1.15.11+~1.14.4-2",
"evidence": "/affected/2/versions"
},
{
"value": "1.15.9+~1.14.4-1",
"evidence": "/affected/2/versions"
},
{
"value": "1.16.0+~1.14.4-1",
"evidence": "/affected/2/versions"
},
{
"value": "1.16.0+~1.14.4-2",
"evidence": "/affected/2/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "DEBIAN-CVE-2026-111756",
"aliases": [
"DEBIAN-CVE-2026-111756"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "node-follow-redirects",
"purl": "pkg:deb/debian/node-follow-redirects?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"1.15.11+~1.14.4-1",
"1.15.11+~1.14.4-2",
"1.15.2+~1.14.1-1",
"1.15.3+~1.14.2-1",
"1.15.6+~1.14.4-1",
"1.15.6+~1.14.4-2",
"1.15.9+~1.14.4-1",
"1.16.0+~1.14.4-1",
"1.16.0+~1.14.4-2",
"1.16.1+~1.14.4-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-111756.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "node-follow-redirects",
"purl": "pkg:deb/debian/node-follow-redirects?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"versions": [
"1.15.11+~1.14.4-1",
"1.15.11+~1.14.4-2",
"1.15.9+~1.14.4-1",
"1.16.0+~1.14.4-1",
"1.16.0+~1.14.4-2",
"1.16.1+~1.14.4-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-111756.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.16.1+~1.14.4-1"
}
]
}
],
"package": {
"name": "node-follow-redirects",
"purl": "pkg:deb/debian/node-follow-redirects?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"1.15.11+~1.14.4-1",
"1.15.11+~1.14.4-2",
"1.15.9+~1.14.4-1",
"1.16.0+~1.14.4-1",
"1.16.0+~1.14.4-2"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-111756.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-27T17:00:06.237690394Z",
"provider": "osv",
"upstream": [
"CVE-2026-111756"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-111756"
]
},
"related_cves": [
{
"value": "CVE-2026-111756",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 462894,
"published_at": "2026-10-20T18:17:18.07+00:00"
}