Skip to content
Fencer Intel
medium 5.9

CVE-2026-116689 json

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

published 13d ago modified 10d ago also EUVD-2026-111363 , GHSA-mrwp-f3q8-3g9p

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm follow-redirects 1.16.2
  • follow-redirects_project follow-redirects 1.16.2
  • follow-redirects follow_redirects 1.16.2
  • agama-web-ui openSUSE Tumbleweed 25+475.275dd4727-56.1

opensuse advisories openSUSE-SU-2026:12424-1

Is CVE-2026-116689 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-116689 updated cvss 5.9

follow-redirects: follow-redirects: Information disclosure via cross-origin redirects

  • Red Hat Hardened Images prometheus3.5 3.5.5-0.9.hum1
    affected: no fix planned “Will not fix”
  • Red Hat Hardened Images grafana13.1 13.1.8-0.6.hum1, grafana13.2 13.2.4-0.6.hum1, grafana12.4 12.4.13-0.6.hum1, prometheus3.13 3.13.5-0.3.hum1
    fixed: vendor fix RHSA-2026:93601

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
10d ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-mrwp-f3q8-3g9p referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm follow-redirects
>=1.16.0, <1.16.2
1.16.2

Affected products

  • follow-redirects follow-redirects

Classification

Weakness
  • CWE-201 Insertion of Sensitive Information Into Sent Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.