CVE-2024-37891: urllib3's Proxy-Authorization request header isn't stripped during cross-origin redirects
When using urllib3's proxy support with ProxyManager, the Proxy-Authorization header is only sent to the configured proxy, as expected. However, when sending HTTP requests without using urllib3's proxy support, it's possible to accidentally configure the Proxy-Authorization header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy.
Published Jun 17, 2024 · Updated Nov 4, 2025
Affected packages
urllib3
- Ecosystem
- PyPI
- Affected
- < 1.26.19
- Fixed in
- 1.26.19
- Check
pip show urllib3
urllib3
- Ecosystem
- PyPI
- Affected
- >= 2.0.0, < 2.2.2
- Fixed in
- 2.2.2
- Check
pip show urllib3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
When using urllib3's proxy support with ProxyManager, the Proxy-Authorization header is only sent to the configured proxy, as expected.
However, when sending HTTP requests *without* using urllib3's proxy support, it's possible to accidentally configure the Proxy-Authorization header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the Proxy-Authorization HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects.
Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the Proxy-Authorization header during cross-origin redirects to avoid the small chance that users are doing this on accident.
Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the Proxy-Authorization header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach.
Affected usages
We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited:
- Setting the
Proxy-Authorizationheader without using urllib3's built-in proxy support. - Not disabling HTTP redirects.
- Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin.
Remediation
- Using the
Proxy-Authorizationheader with urllib3'sProxyManager. - Disabling HTTP redirects using
redirects=Falsewhen sending requests. - Not using the
Proxy-Authorizationheader.
Credited to pquentin, illia-v, G-Rath.
References
- https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf
- https://nvd.nist.gov/vuln/detail/CVE-2024-37891
- https://github.com/urllib3/urllib3/commit/40b6d1605814dd1db0a46e202d6e56f2e4c9a468
- https://github.com/urllib3/urllib3/commit/accff72ecc2f6cf5a76d9570198a93ac7c90270e
- https://lists.debian.org/debian-lts-announce/2024/12/msg00020.html
- https://security.netapp.com/advisory/ntap-20240822-0003
- https://www.vicarius.io/vsociety/posts/proxy-authorization-header-handling-vulnerability-in-urllib3-cve-2024-37891
- https://github.com/advisories/GHSA-34jh-p97f-mpxf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-97687
urllib3: HTTPS proxy TLS configuration may be ignored or overridden
high7.6Sep 30, 2026CVE-2026-97688
urllib3: Chunked Deflate streaming can enter an infinite loop
medium6.9Sep 30, 2026CVE-2026-97689
urllib3: HTTPResponse.stream()/read_chunked() buffers an unbounded chunk-size line into memory
high8.9Sep 30, 2026CVE-2026-44431
urllib3: Sensitive headers forwarded across origins in proxied low-level redirects
high5.3May 11, 2026CVE-2026-44432
urllib3: Decompression-bomb safeguards bypassed in parts of the streaming API
high7.5May 11, 2026CVE-2026-21441
Decompression-bomb safeguards bypassed when following HTTP redirects (streaming API)
high7.5Jan 7, 2026
