GHSA-q3jh-wrc6-jgq8: follow-redirects (CVE-2026-111756)

Package	Ecosystem	Affected	Fixed in
follow-redirects	npm	>=1.16.0, <1.16.1	1.16.1

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

follow-redirects versions from 1.16.0 before 1.16.1 fail to strip credential headers, such as Authorization, Cookie and Proxy-Authorization, when the caller supplies headers as an array, a form Node's http.request accepts. An attacker who controls a redirect target that the application contacts can receive those headers after a cross-origin redirect, and in cleartext on a protocol downgrade. Upgrade to follow-redirects 1.16.1.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
8.2	High	4.0	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	CNA (GitHub_M)

CISA KEV Not listed.
EPSS 0.0047, the 40th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

31 Oct 2026, 13:33 UTC First seen by agentprime
31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.