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, Cooki…
Exact source revision recorded 5 Nov 2026 04:01:07 UTC. It does not establish the source's current position. Latest evidence.
euvd · EUVD-2026-105225
Publishedfollow-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.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 20, 2026, 5:58:21 PM
dateUpdated: Oct 23, 2026, 1:59:26 AM
4 related source bulletins · separate from aliases
openSUSE-SU-2026:12261-1: git-bug-0.11.0-3.1 on GA media
CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-110816 · CVE-2026-111756 · CVE-2026-112085 · CVE-2026-112366 · CVE-2026-78659 · CVE-2026-78660 · CVE-2026-78663 · CVE-2026-78669 · CVE-2026-97032
RHSA-2026:88537: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-65627 · CVE-2026-111755 · CVE-2026-111756 · CVE-2026-114125 · CVE-2026-114126
RHSA-2026:88478: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-111755 · CVE-2026-111756 · CVE-2026-114125 · CVE-2026-114126
RHSA-2026:88541: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-40895 · CVE-2026-65627 · CVE-2026-111755 · CVE-2026-111756 · CVE-2026-114125 · CVE-2026-114126
- Source published
- Oct 20, 2026, 5:58:21 PM (timezone not stated)
- Source modified
- Oct 23, 2026, 1:59:26 AM (timezone not stated)
- Observed here
- 5 Nov 2026 04:01:07 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 4.0 · 8.2 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