Skip to main content
VulnerabilityPublished Updated

CVE-2026-40895: follow-redirects · Information Exposure

Affects follow-redirectsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.16.0 when convenient.

Data as of 2 Nov 2026, 23:43 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Sources agree

CVSS scores by source
CNA (GitHub_M)CVSS 4.06.9
ADP (redhat-SADP)CVSS 3.17.5
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-04-22.

Patch
Available – fixed in 1.16.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 2 Nov 2026.

What to do

Upgrade follow-redirects to 1.16.0.

Affected software

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

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.0 or later, where this issue is fixed by properly stripping custom authentication headers on cross-domain redirects. Until upgraded, avoid sending sensitive custom authentication headers in requests that may be redirected across domains. Red Hat notes that no alternative mitigations meet their criteria, so patching is the recommended action.

Description

The follow-redirects npm package prior to version 1.16.0 improperly forwards custom authentication headers such as X-API-Key or X-Auth-Token during cross-domain HTTP redirects. This behavior can lead to unintended disclosure of sensitive authentication information to untrusted redirect targets. The issue is fixed in version 1.16.0.

References

Community reviews

Loading reviews…