Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 20 Oct 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-212 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Mon, 19 Oct 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Follow-redirects
Follow-redirects follow Redirects |
|
| Vendors & Products |
Follow-redirects
Follow-redirects follow Redirects |
Mon, 19 Oct 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 19 Oct 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | follow-redirects sensitiveHeaders regex escaping can expose credential headers | |
| Weaknesses | CWE-185 CWE-200 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-19T18:00:16.343Z
Reserved: 2026-10-16T17:52:09.081Z
Link: CVE-2026-111755
Updated: 2026-10-19T18:00:06.589Z
Status : Awaiting Analysis
Published: 2026-10-19T18:17:00.260
Modified: 2026-10-19T21:13:39.973
Link: CVE-2026-111755
OpenCVE Enrichment
Updated: 2026-10-19T20:30:03Z