Skip to main content
VulnerabilityPublished

CVE-2026-116689: follow-redirects · Insertion of Sensitive Information Into Sent Data

Affects follow-redirectsSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.16.2 when convenient.

Data as of 27 Oct 2026, 20:12 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.16.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade follow-redirects to 1.16.2.

Affected software

ProductAffectedFixed in
follow-redirectsfollow-redirectsAffected
  • >=1.16.0 <1.16.2
Fixed in
  • 1.16.2
npmfollow-redirectspkg:npm/follow-redirectsOther threatsAffected
  • >=1.16.0 <1.16.2
Fixed in
  • 1.16.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade follow-redirects to version 1.16.2 or later, where the issue is fixed. No other mitigation is indicated or necessary.

Description

A vulnerability in the follow-redirects Node.js library versions 1.16.0 through 1.16.1 allows sensitive headers to be improperly forwarded during cross-origin redirects. This occurs because the sensitiveHeaders option is checked using value instanceof Array, which fails for arrays created in different JavaScript realms, causing the sensitive headers list to be replaced with an empty array. As a result, custom credential headers can be sent to attacker-controlled redirect destinations. The issue is fixed in version 1.16.2.

References

Community reviews

Loading reviews…