# CVE-2026-111756: follow-redirects array-form headers bypass cross-origin credential stripping


- **Severity:** High 8.2 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-109829, AZL-110088, DEBIAN-CVE-2026-111756, ECHO-9da0-e484-8d88, GHSA-q3jh-wrc6-jgq8, MINI-2rvw-pfpv-53cf, MINI-4r86-6f8f-4p63, MINI-6r43-vqjc-683q, MINI-ch3q-hj3f-2798, MINI-fp2x-j967-9c8x, MINI-hrm8-mhq5-4prf, MINI-ppxj-3c8m-xhjv, ROOT-APP-NPM-CVE-2026-111756, UBUNTU-CVE-2026-111756

## What is CVE-2026-111756?

CVE-2026-111756 is a high-severity vulnerability in follow-redirects, published on 20 Oct 2026. 

### Official 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.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-111756?

2 open source packages ship an affected version, including follow-redirects.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `follow-redirects` | npm | From 1.16.0 | 1.16.1 |
| `follow-redirects` | npm | From 1.16.0 | 1.16.1 |

## How do I fix CVE-2026-111756?

Upgrade follow-redirects to 1.16.1 or later.

## Is CVE-2026-111756 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111756 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111756 and fix it if it is affected.

What it is: CVE-2026-111756 is a high-severity vulnerability in follow-redirects, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111756 exists.

Affected packages and fixed versions:
- follow-redirects (npm): affected from 1.16.0; fixed in 1.16.1
- follow-redirects (npm): affected from 1.16.0; fixed in 1.16.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111756/ (Markdown: https://insights.sbomify.com/CVE-2026-111756/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111756
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111756
- OSV: https://osv.dev/vulnerability/CVE-2026-111756

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111756/
Summaries are generated and may contain mistakes; the official description above is the record.