urllib3 Sensitive Header Leak in Low-Level Redirects (CVE-2026-44431)

The urllib3 library, a popular Python HTTP client, is vulnerable to sensitive header leakage (CVE-2026-44431) when handling cross-origin redirects in its low-level API. Specifically, when applications use HTTPConnection.urlopen() instances created via ProxyManager.connection_from_url() and allow cross-origin redirects, sensitive headers like Authorization, Cookie, and Proxy-Authorization are inadvertently forwarded to the redirect destination. This behavior can expose sensitive credentials to unintended third-party servers. This vulnerability affects urllib3 versions before 2.7.0. Defenders should prioritize upgrading urllib3 to version 2.7.0 or later to mitigate this risk and ensure proper handling of sensitive headers during redirects. If immediate upgrade is not feasible, applications should avoid using the vulnerable low-level redirect flow for cross-origin redirects and consider switching to ProxyManager.request() instead.

Attack Chain

1. The attacker controls a malicious website or compromises an existing one.
2. A user’s application (using a vulnerable urllib3 version) initiates an HTTP request to a controlled domain.
3. The attacker’s server responds with an HTTP 302 redirect to a different, attacker-controlled origin.
4. The application, using ProxyManager.connection_from_url().urlopen(..., assert_same_host=False), follows the redirect.
5. Due to the vulnerability, the application inappropriately forwards sensitive headers (Authorization, Cookie, Proxy-Authorization) along with the redirected request.
6. The attacker’s server receives the forwarded request containing the sensitive headers, potentially including authentication tokens or session IDs.
7. The attacker captures and logs these sensitive headers.
8. The attacker uses the captured credentials to impersonate the user or gain unauthorized access to protected resources.

Impact

Successful exploitation of this vulnerability (CVE-2026-44431) can lead to the exposure of sensitive user credentials, including authentication tokens and session cookies. The impact ranges from account compromise to unauthorized access to sensitive data and resources. The number of potential victims depends on the adoption rate of vulnerable urllib3 versions and the frequency with which applications utilize the susceptible low-level redirect flow. Applications that handle authentication or authorization via HTTP headers are particularly at risk.

Recommendation

• Upgrade to urllib3 version 2.7.0 or later to remediate the vulnerability (CVE-2026-44431), where sensitive headers are stripped from redirects followed by HTTPConnection.
• If upgrading is not immediately possible, avoid using the low-level redirect flow (ProxyManager.connection_from_url().urlopen(..., assert_same_host=False)) for cross-origin redirects.
• Consider switching to ProxyManager.request() if appropriate for your use case, as this high-level API strips sensitive headers during redirects by default.
• Deploy the Sigma rule “Detect urllib3 Low-Level API Cross-Origin Redirect with Sensitive Headers” to detect potential exploitation attempts by monitoring for the vulnerable code pattern.