Bug 2555733 (CVE-2026-111755) - CVE-2026-111755 follow-redirects: follow-redirects: Information disclosure via improper regular expression escaping in sensitive header filtering
Summary: CVE-2026-111755 follow-redirects: follow-redirects: Information disclosure vi...
Keywords:
Status: NEW
Alias: CVE-2026-111755
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-19 17:42 UTC by OSIDB Bzimport
Modified: 2026-10-19 17:50 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-19 17:42:28 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.