[From nobody Sat Oct 24 21:45:06 2026
Received: (at submit) by bugs.debian.org; 24 Oct 2026 19:17:18 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-108.4 required=4.0 tests=ALL_TRUSTED,BAYES_00,
 DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
 FOURLA,FROMDEVELOPER,MD5_SHA1_SUM,SPF_HELO_NONE,SPF_PASS,
 USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 150; neutral, 112; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: &lt;carnil@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:40972)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xKhF1-001IKZ-1s
 for submit@bugs.debian.org; Sat, 24 Oct 2026 19:17:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=1YPdltpmvqqNQWORpwlTeRfV+IDGKUcTF7QYzAJD+zU=; b=C7bGoOsJjr78XAjQcm1RlFvLBa
 I0bIOzZwxQlPXL2642T/0uCHHyBX6i4mCwWPgPBXcQC1mQaZURzltPal0injn2/T3FSKif3nosXZ7
 L0dy7TnjQtqkrwM8jeweJmuNXIU7LHmqw+DEAObwiPcox03f8wak3yP2s38SohGTKvAgwbAfQLngM
 xESgwqZn5BjmXbEzgZDE+EryoYGkx6FZwKzf8TWocQIXe00lEqoUiSjVO69kXCco32LX6KvxhY96l
 I7+aPkkMT27FEt6v5b+Anmd+OVIL7TMM6wB07Gpqvw/yS5YvK+JdFGoQmv2yrVJI4QY3Ki8LyoqEO
 /F44/a3w==;
Received: from authenticated-user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xKhEy-004EDu-1q
 for submit@bugs.debian.org; Sat, 24 Oct 2026 19:17:17 +0000
Received: by eldamar.lan (Postfix, from userid 1000)
 id 30159DC08A9; Sat, 24 Oct 2026 21:17:16 +0200 (CEST)
Date: Sat, 24 Oct 2026 21:17:16 +0200
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: submit@bugs.debian.org
Subject: node-follow-redirects: CVE-2026-111756
Message-ID: &lt;at0EPEZIlJWN2xCn@eldamar.lan&gt;
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: carnil
Delivered-To: submit@bugs.debian.org

Source: node-follow-redirects
Version: 1.16.0+~1.14.4-2
X-Debbugs-CC: team@security.debian.org
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for node-follow-redirects.

CVE-2026-111756[0]:
| follow-redirects is a Node.js HTTP and HTTPS client wrapper that
| automatically follows redirects. From version 1.16.0 to before
| version 1.16.1, follow-redirects removes sensitive credential
| headers (Authorization, Proxy-Authorization, Cookie, and any caller-
| declared sensitiveHeaders) before following a redirect that crosses
| to a different host or downgrades to a less secure protocol. The
| removal routine iterates the caller's headers container with
| for...in and matches header names against a filter. This assumes the
| headers container is a plain object keyed by header names. Node's
| underlying http.request, which follow-redirects is a drop-in
| replacement for, also accepts headers as an alternating array of
| names and values. For an array, for...in yields the numeric indices
| &quot;0&quot;, &quot;1&quot;, &quot;2&quot; and so on, which never match a header-name filter, so
| nothing is removed. An application that sends array-form headers and
| follows an attacker-controlled cross-origin redirect therefore
| forwards its Authorization, Cookie, and Proxy-Authorization headers
| verbatim to the attacker-controlled destination, with no error or
| warning. The sensitiveHeaders option added to fix CVE-2026-40895 /
| GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the
| same helper. This is an unauthenticated confidentiality
| vulnerability: any remote server the victim application contacts can
| harvest the victim's credential headers by responding with a cross-
| origin redirect. This issue has been patched in version 1.16.1.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-111756
    https://www.cve.org/CVERecord?id=CVE-2026-111756
[1] https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-q3jh-wrc6-jgq8
[2] https://github.com/follow-redirects/follow-redirects/commit/9865ca45490e4d0f7b6944870318408344570aff

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]