cve.bz

CVE-2026-111756 follow-redirects follow-redirects

8.2 highEPSS 0.5%Fix available

High (8.2) in follow-redirects follow-redirects. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in follow-redirects 1.16.1.

On this page
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.

Severity

CVSS 4.0

8.2 high
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
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-212 Improper Removal of Sensitive Information Before Storage or Transfer
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-111756 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111756?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111756?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111756 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
follow-redirects>= 1.16.0, < 1.16.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q3jh-wrc6-jgq8npmfollow-redirects>=1.16.0 <1.16.11.16.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13node-follow-redirectsno fix listedDEBIAN-CVE-2026-111756
Debian14node-follow-redirects1.16.1+~1.14.4-1DEBIAN-CVE-2026-111756
Ubuntu26.10, Pro:18.04:LTS, Pro:20.04:LTS and 3 morenode-follow-redirectsno fix listedUBUNTU-CVE-2026-111756
Red Hathummingbird:1grafana12.40:12.4.13-0.3.hum1RHSA-2026:88478
Red Hathummingbird:1grafana13.10:13.1.8-0.4.hum1RHSA-2026:88537
Red Hathummingbird:1grafana13.20:13.2.4-0.3.hum1RHSA-2026:88541
openSUSETumbleweedagama-web-ui25+475.275dd4727-56.1openSUSE-SU-2026:12424-1
openSUSETumbleweedgit-bug0.11.0-3.1openSUSE-SU-2026:12261-1
Azure Linux3js-jqueryno fix listedAZL-109829
Azure Linux3python-tensorboardno fix listedAZL-110088

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat has evaluated this vulnerability as an Important severity impact because unauthenticated remote servers can harvest sensitive authorization credentials when following cross-origin redirects without requiring user interaction. Client applications utilizing this library to query untrusted endpoints while supplying headers in array structures inadvertently expose credentials across differing origins or insecure transport channels. The risk is constrained to scenarios where services perform outbound requests to external, untrusted hosts using this specific header format.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-10-20) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to format all outgoing HTTP request headers as plain key-value objects rather than alternating arrays when invoking follow-redirects: upgrade to follow-redirects 1.16.1 (or the fixed Prometheus/Grafana builds), which detect if options.headers is an array and convert alternating name-value pairs into a plain JavaScript object before sanitizing and stripping headers, closing all 2 injection vectors (cross-origin HTTP redirect, protocol downgrade redirect). Until patched, this is a concern on Applications on any platform issuing requests with array-formatted sensitive headers via follow-redirects, so Configure outgoing requests to pass headers strictly as plain objects instead of alternating arrays and avoid contacting untrusted endpoints capable of triggering cross-origin redirects. These controls limit blast radius and contain exploitation, but they do not fix the underlying array-formatted header stripping bypass defect — apply the upstream patch to fully remediate.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgrafana12-4-main-12.4.13-0.3.hum1Fixed 2026-10-23RHSA-2026:88478
Red Hat Hardened Imagesgrafana13-1-main-13.1.8-0.4.hum1Fixed 2026-10-23RHSA-2026:88537
Red Hat Hardened Imagesgrafana13-2-main-13.2.4-0.3.hum1Fixed 2026-10-23RHSA-2026:88541
Red Hat Hardened Imagesprometheus3.13Not affected
Red Hat Hardened Imagesprometheus3.5Will not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-111756.

Attack patterns (CAPEC)

  • CAPEC-168 Windows ::DATA Alternate Data Stream Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON