Quick answers
- Is CVE-2026-116689 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116689 being exploited in the wild.
- How severe is CVE-2026-116689?
- Medium severity, with a CVSS score of 5.9, published 27 October 2026.
- Which products and versions are affected?
- Follow-Redirects 1.16.0 to 1.16.1; follow-redirects (npm) >= 1.16.0, <= 1.16.1, SEMVER:introduced=1.16.0,fixed=1.16.2.
- Is there a fix for CVE-2026-116689?
- Yes. follow-redirects (npm): upgrade to 1.16.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116689 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116689?
- 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.2 or later
npm install follow-redirects@1.16.2
Technical details
The vulnerability stems from improper array type-checking: the sensitiveHeaders option is validated using the instanceof Array operator instead of Array.isArray(), allowing arrays created in different JavaScript realms to bypass the check and be replaced with an empty list. When a cross-origin redirect occurs, credential headers that should have been filtered are forwarded to the redirect destination, violating security boundaries.
Affected products
- follow-redirects follow-redirects 1.16.0 to 1.16.1
Identifiers
- CVE-2026-116689
- GHSA-mrwp-f3q8-3g9p
Timeline
- 2026-10-27: disclosed