CVE-2026-111755

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-111755
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-111755.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-111755
Aliases
  • GHSA-8r9p-f939-6h3c
Published
2026-10-19T17:27:09Z
Modified
2026-10-20T02:44:45Z
Severity
  • 8.2 (High) CVSS_V4 - 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 CVSS Calculator
Summary
follow-redirects sensitiveHeaders regex escaping can expose credential headers
Details

follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.

Database specific 
{
    "cna_assigner":  "GitHub_M",
    "cwe_ids":  [
        "CWE-185",
        "CWE-200"
    ],
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/111xxx/CVE-2026-111755.json"
}
References

Affected packages

Git / github.com/follow-redirects/follow-redirects

Affected ranges

Type
GIT
Repo
https://github.com/follow-redirects/follow-redirects
Events
Introduced
0c23a223067201c368035e82954c11eb2578a33b
Fixed
46301256333c90b7faac7aa126effe72ec16d16e
Database specific
Show details 
{
    "extracted_events":  [
        {
            "introduced":  "1.16.0"
        },
        {
            "fixed":  "1.16.1"
        }
    ],
    "source":  "AFFECTED_FIELD"
}

Affected versions

v1.*
v1.16.0

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-111755.json"