UBUNTU-CVE-2026-111756 (CVE-2026-111756)
Vulnerability from osv_ubuntu – Published: 2026-10-20 18:17 – Updated: 2026-10-28 17:50 – Source websitefollow-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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-follow-redirects",
"binary_version": "1.2.4-1ubuntu0.18.04.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "node-follow-redirects",
"purl": "pkg:deb/ubuntu/node-follow-redirects@1.2.4-1ubuntu0.18.04.1~esm2?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.4-1",
"1.2.4-1ubuntu0.18.04.1~esm1",
"1.2.4-1ubuntu0.18.04.1~esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-follow-redirects",
"binary_version": "1.2.4-1ubuntu0.20.04.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "node-follow-redirects",
"purl": "pkg:deb/ubuntu/node-follow-redirects@1.2.4-1ubuntu0.20.04.1~esm2?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.4-1",
"1.2.4-1ubuntu0.20.04.1~esm1",
"1.2.4-1ubuntu0.20.04.1~esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-follow-redirects",
"binary_version": "1.14.9+~1.14.1-1ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "node-follow-redirects",
"purl": "pkg:deb/ubuntu/node-follow-redirects@1.14.9+~1.14.1-1ubuntu0.1~esm2?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.13.1-1",
"1.14.5-1",
"1.14.7+~1.13.1-1",
"1.14.8+~1.14.0-1",
"1.14.9+~1.14.1-1",
"1.14.9+~1.14.1-1ubuntu0.1~esm1",
"1.14.9+~1.14.1-1ubuntu0.1~esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-follow-redirects",
"binary_version": "1.15.6+~1.14.4-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "node-follow-redirects",
"purl": "pkg:deb/ubuntu/node-follow-redirects@1.15.6+~1.14.4-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"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-1ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-follow-redirects",
"binary_version": "1.16.0+~1.14.4-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "node-follow-redirects",
"purl": "pkg:deb/ubuntu/node-follow-redirects@1.16.0+~1.14.4-2?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.15.11+~1.14.4-1build1",
"1.16.0+~1.14.4-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-follow-redirects",
"binary_version": "1.15.11+~1.14.4-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:26.04:LTS",
"name": "node-follow-redirects",
"purl": "pkg:deb/ubuntu/node-follow-redirects@1.15.11+~1.14.4-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.15.9+~1.14.4-1",
"1.15.11+~1.14.4-1build1",
"1.15.11+~1.14.4-1ubuntu0.1~esm1"
]
}
],
"aliases": [],
"details": "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\u0027s 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\u0027s 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\u0027s credential headers by responding with a cross-origin redirect. This issue has been patched in version 1.16.1.",
"id": "UBUNTU-CVE-2026-111756",
"modified": "2026-10-28T17:50:35Z",
"published": "2026-10-20T18:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-111756"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111756"
},
{
"type": "REPORT",
"url": "https://github.com/follow-redirects/follow-redirects"
},
{
"type": "REPORT",
"url": "https://github.com/follow-redirects/follow-redirects/commit/9865ca45490e4d0f7b6944870318408344570aff"
},
{
"type": "REPORT",
"url": "https://github.com/follow-redirects/follow-redirects/releases/tag/v1.16.1"
},
{
"type": "REPORT",
"url": "https://github.com/follow-redirects/follow-redirects/security/advisories/ghsa-q3jh-wrc6-jgq8"
},
{
"type": "REPORT",
"url": "https://advisory.echohq.com/cve/cve-2026-111756"
},
{
"type": "REPORT",
"url": "https://github.com/cveproject/cvelistv5/tree/main/cves/2026/111xxx/cve-2026-111756.json"
},
{
"type": "REPORT",
"url": "https://nvd.nist.gov/vuln/detail/cve-2026-111756"
},
{
"type": "REPORT",
"url": "https://security-tracker.debian.org/tracker/cve-2026-111756"
},
{
"type": "REPORT",
"url": "https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151931"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"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",
"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",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-111756"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.