Skip to main content
VulnerabilityPublished Updated

CVE-2026-111756: Node follow redirects · follow-redirects is a Node.js HTTP and HTTPS client wrapper that

Affects node-follow-redirectsSource GCVE Database

0

Mentioned vulnerabilities

Authoritative record:CVE-2026-111756· High 8.2

Not known to be exploited · CVSS 8.2 High · fixed in 1.16.1 : patch node-follow-redirects soon.

Data as of 28 Oct 2026, 22:31 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.16.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 20 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CISA SSVC: proof of concept public

  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

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 4 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 3 days after disclosure

  4. In Threat Radar

    record ingested

    , 6 days after disclosure

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

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10node-follow-redirectspkg:deb/ubuntu/node-follow-redirects?arch=source&distro=stonkingOther threatsAffected
  • =1.15.11+~1.14.4-1build1
  • =1.16.0+~1.14.4-2
Fixed in–
Ubuntu Pro 26.04 LTSnode-follow-redirectspkg:deb/ubuntu/node-follow-redirects?arch=source&distro=esm-apps/resoluteOther threatsAffected
  • =1.15.9+~1.14.4-1
  • =1.15.11+~1.14.4-1build1
  • =1.15.11+~1.14.4-1ubuntu0.1~esm1
Fixed in–
Ubuntu Pro 24.04 LTSnode-follow-redirectspkg:deb/ubuntu/node-follow-redirects?arch=source&distro=esm-apps/nobleOther threatsAffected
  • 1.15.2+~1.14.1-1 – 1.15.6+~1.14.4-1ubuntu0.1~esm1
4 affected builds
Fixed in–
Ubuntu Pro 22.04 LTSnode-follow-redirectspkg:deb/ubuntu/node-follow-redirects?arch=source&distro=esm-apps/jammyOther threatsAffected
  • 1.13.1-1 – 1.14.9+~1.14.1-1ubuntu0.1~esm2
7 affected builds
Fixed in–
Ubuntu Pro 20.04 LTSnode-follow-redirectspkg:deb/ubuntu/node-follow-redirects?arch=source&distro=esm-apps/focalOther threatsAffected
  • =1.2.4-1
  • =1.2.4-1ubuntu0.20.04.1~esm1
  • =1.2.4-1ubuntu0.20.04.1~esm2
Fixed in–
Ubuntu Pro 18.04 LTSnode-follow-redirectspkg:deb/ubuntu/node-follow-redirects?arch=source&distro=esm-apps/bionicOther threatsAffected
  • =1.2.4-1
  • =1.2.4-1ubuntu0.18.04.1~esm1
  • =1.2.4-1ubuntu0.18.04.1~esm2
Fixed in–

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

Description

follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From version 1.16.0 to before version 1.16.1, follow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared sensitiveHeaders) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller's headers container with for...in and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node's underlying http.request, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, for...in yields the numeric indices "0", "1", "2" and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The sensitiveHeaders option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerability: any remote server the victim application contacts can harvest the victim's credential headers by responding with a cross-origin redirect. This issue has been patched in version 1.16.1.

References

Community reviews

Loading reviews…