CVSS 4.0
8.2 highCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NHigh (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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:Nfollow-redirects (npm): fixed in 1.16.1Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| follow-redirects | >= 1.16.0, < 1.16.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-q3jh-wrc6-jgq8 | npm | follow-redirects | >=1.16.0 <1.16.1 | 1.16.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | node-follow-redirects | no fix listed | DEBIAN-CVE-2026-111756 |
| Debian | 14 | node-follow-redirects | 1.16.1+~1.14.4-1 | DEBIAN-CVE-2026-111756 |
| Ubuntu | 26.10, Pro:18.04:LTS, Pro:20.04:LTS and 3 more | node-follow-redirects | no fix listed | UBUNTU-CVE-2026-111756 |
| Red Hat | hummingbird:1 | grafana12.4 | 0:12.4.13-0.3.hum1 | RHSA-2026:88478 |
| Red Hat | hummingbird:1 | grafana13.1 | 0:13.1.8-0.4.hum1 | RHSA-2026:88537 |
| Red Hat | hummingbird:1 | grafana13.2 | 0:13.2.4-0.3.hum1 | RHSA-2026:88541 |
| openSUSE | Tumbleweed | agama-web-ui | 25+475.275dd4727-56.1 | openSUSE-SU-2026:12424-1 |
| openSUSE | Tumbleweed | git-bug | 0.11.0-3.1 | openSUSE-SU-2026:12261-1 |
| Azure Linux | 3 | js-jquery | no fix listed | AZL-109829 |
| Azure Linux | 3 | python-tensorboard | no fix listed | AZL-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 rates this Important.
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.
--- 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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | grafana12-4-main-12.4.13-0.3.hum1 | Fixed 2026-10-23 | RHSA-2026:88478 |
| Red Hat Hardened Images | grafana13-1-main-13.1.8-0.4.hum1 | Fixed 2026-10-23 | RHSA-2026:88537 |
| Red Hat Hardened Images | grafana13-2-main-13.2.4-0.3.hum1 | Fixed 2026-10-23 | RHSA-2026:88541 |
| Red Hat Hardened Images | prometheus3.13 | Not affected | |
| Red Hat Hardened Images | prometheus3.5 | Will 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.
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).