CVE-2026-111755: high-severity vulnerability in follow-redirects
follow-redirects sensitiveHeaders regex escaping can expose credential headers
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.2epss 0.5%
follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.
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
Affected products
follow-redirects · follow-redirectsRelated CVEs — follow-redirects
In the same product, most dangerous first.
CVE-2024-28849MEDIUMProxy-Authorization header kept across hosts in follow-redirectsEPSS 1.0%CVE-2026-40895MEDIUMfollow-redirects: Custom Authentication Headers Leaked to Cross-Domain Redirect TargetsEPSS 0.5%CVE-2026-111756HIGHfollow-redirects array-form headers bypass cross-origin credential strippingEPSS 0.5%CVE-2026-116689MEDIUMfollow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirectsEPSS 0.3%