CVE-2026-116689

follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects

Published Oct 27, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The follow-redirects Node.js HTTP/HTTPS client wrapper incorrectly handles sensitiveHeaders arrays that are created in a different JavaScript realm. From version 1.16.0 up to but not including 1.16.2, the check uses instanceof Array, which replaces such cross-realm arrays with an empty list. When a request follows an attacker-controlled redirect, a custom credential header listed in the discarded array can be forwarded to the redirect destination, potentially exposing private credentials or authentication tokens to unintended parties.

Affected Systems

This vulnerability impacts applications that import the follow-redirects library and use sensitiveHeaders configurations in versions 1.16.0 through 1.16.1. Legacy installations or environments that rely on these versions should be upgraded to 1.16.2 or later to eliminate the risk.

Risk and Exploitability

The CVSS score of 5.9 indicates a medium severity problem. The EPSS score is 0.00266 and the vulnerability is not listed in the CISA KEV catalog. An attacker needs to control the redirect target and supply a cross-realm array in the sensitiveHeaders option to trigger the flaw. Successful exploitation would allow the attacker to cause confidential headers to be forwarded to a third‑party domain, leading to potential credential leakage.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade follow-redirects to version 1.16.2 or newer.
  • If an immediate upgrade is not feasible, avoid using custom sensitiveHeaders that reference cross‑realm arrays when following redirects from untrusted origins.
  • Manually validate sensitiveHeaders by converting arrays with Array.isArray before passing them to the library to ensure they are not discarded.

Generated by OpenCVE AI on October 29, 2026 at 14:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-mrwp-f3q8-3g9p follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Follow-redirects
Follow-redirects follow Redirects
Vendors & Products Follow-redirects
Follow-redirects follow Redirects
Type Values Removed Values Added
Description 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.
Title follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects
Weaknesses CWE-201
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-201

    Insertion of Sensitive Information Into Sent Data

  • CWE-212

    Improper Removal of Sensitive Information Before Storage or Transfer

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 6:47 PM
Reserved
Oct 26, 2026, 8:00 PM
Status
Deferred
Published
Oct 27, 2026, 8:17 PM
Modified
Oct 30, 2026, 7:18 PM
Severity
Moderate
Public date
Oct 27, 2026, 7:38 PM