CVE-2026-111755

8.2High

Published 19 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash

8.2High

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: High impact on confidentiality
Weakness: CWE-185, CWE-200

Impact

Remote attackers operating a redirect target can steal sensitive headers and credentials. They just need the client application to follow a cross-origin or HTTPS-to-HTTP redirect to their server.

Root cause

The escapeRegex utility fails to escape regex metacharacters (^ and |) in sensitiveHeaders, causing header-filtering regular expressions to miss matching sensitive header names.

Affected systems

follow-redirects 1.16.0 up to (excluding) 1.16.1

CVSS v4.0 · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade follow-redirects to version 1.16.1. If you cannot patch immediately, avoid using header names that include ^ or | in sensitiveHeaders configurations.

shell

$ npm install follow-redirects@1.16.1

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-111755