Answer in brief
CVE-2026-116689 records a Medium severity (CVSS 5.9) vulnerability in follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects. The current sources do not mark it as known exploited. The current feed maps follow-redirects/follow-redirects (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps follow-redirects/follow-redirects (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| follow-redirects/follow-redirectsgeneric | >=1.16.0 <1.16.2 | 1.16.2 |
Published upstream
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 27, 2026
follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.
Quoted source text, attributed separately from HOL analysis.