Quick answers
- Is CVE-2026-111755 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111755 being exploited in the wild.
- How severe is CVE-2026-111755?
- High severity, with a CVSS score of 4, published 19 October 2026.
- Which products and versions are affected?
- Follow-Redirects 1.16.0 to 1.16.0; follow-redirects (npm) >= 1.16.0, < 1.16.1, SEMVER:introduced=1.16.0,fixed=1.16.1.
- Is there a fix for CVE-2026-111755?
- Yes. follow-redirects (npm): upgrade to 1.16.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111755 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111755?
- Check whether you run Follow-Redirects or follow-redirects (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- follow-redirects (npm): upgrade to 1.16.1 or later
npm install follow-redirects@1.16.1
Technical details
The escapeRegex function in follow-redirects versions 1.16.0 through 1.16.1 failed to escape regular expression metacharacters ^ and | used in sensitiveHeaders configuration, causing regex filters to fail matching sensitive header names containing these characters. When a cross-origin or HTTPS-to-HTTP redirect occurs, unescaped metacharacters prevent the generated filter from matching the intended header name, allowing credential headers to be forwarded to attacker-controlled redirect targets.
Affected products
- follow-redirects follow-redirects 1.16.0 to 1.16.0
Identifiers
- CVE-2026-111755
- GHSA-8r9p-f939-6h3c
Timeline
- 2026-10-19: disclosed
- 2026-10-01: patched: Version 1.16.1 released