All vulnerabilities

npm

CVE-2026-111756

follow-redirects array-form headers bypass cross-origin credential stripping

Severity
High
Published
20 Oct 2026
Last changed
20 Oct 2026
Added to UpHeron
22 Oct 2026
Fixed in
1.16.1
Exploit chance
0.5% in the next 30 daysHigher than 41% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Information exposure (CWE-200)CWE-212
Also known as
GHSA-q3jh-wrc6-jgq8
Sources
OSV.dev and GitHub

Description

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.

From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

Affected software

SoftwareAffected versions
follow-redirectsnpm · osv:npm:follow-redirects
  • From 1.16.0 before 1.16.1

About follow-redirects

Weekly downloads (npm)
145,038,378npm, 17 Nov 2026

Vulnerabilities in follow-redirects

In our list
3
Published in the last 12 months
3
Critical, last 12 months
0
High, last 12 months
2
Known exploited
0
Search the list for follow-redirects

References