{
  "id": "CVE-2026-111756",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-111756",
  "published_at": "2026-10-20T17:58:21.005Z",
  "title": "follow-redirects array-form headers bypass cross-origin credential stripping",
  "vendor": "follow-redirects",
  "product": "follow-redirects",
  "cvss": {
    "score": 8.2,
    "source": "cna",
    "vector": "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-200",
  "cvss_by_source": {
    "cna": 8.2
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "follow-redirects",
        "product": "follow-redirects",
        "ranges": [
          "\u003e= 1.16.0, \u003c 1.16.1"
        ],
        "fixed_in": [
          "1.16.1"
        ]
      }
    ],
    "upgrade": [
      "Upgrade follow-redirects to 1.16.1 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-q3jh-wrc6-jgq8"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/follow-redirects/follow-redirects/commit/9865ca45490e4d0f7b6944870318408344570aff"
      },
      {
        "kind": "Release notes",
        "url": "https://github.com/follow-redirects/follow-redirects/releases/tag/v1.16.1"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
