Skip to content
Connect AISign inSign up free
CVE-2026-1117558.2HighCWE-185

CVE-2026-111755: follow-redirects sensitiveHeaders regex escaping can expose credential headers

follow-redirects

Affected: follow-redirects · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.5%probability of exploitation in the next 30 days
41st percentile
050100

Higher than 41% of scored CVEs

8.2HighCVSS 4.0
LowHigh

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • follow-redirects · follow-redirects>= 1.16.0, < 1.16.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
October 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-111755 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References