CVE-2026-44431: urllib3: Sensitive headers forwarded across origins in proxied low-level redirects

Published May 11, 2026
·
Updated

### Impact When following cross-origin redirects for requests made using urllib3’s high-level APIs, such as `urllib3.request()`, `PoolManager.request()`, and `ProxyManager.request()`, sensitive headers — `Authorization`, `Cookie`, and `Proxy-Authorization` (defined in `Retry.DEFAULT_REMOVE_HEADERS_ON_REDIRECT`) — are stripped by default, as expected. However, cross-origin redirects followed from the low-level API via `ProxyManager.connection_from_url().urlopen(..., assert_same_host=False)` still forward these sensitive headers. ### Affected usage Applications and libraries using urllib3 versions earlier than 2.7.0 may be affected if they allow cross-origin redirects while making requests through `HTTPConnection.urlopen()` instances created via `ProxyManager.connection_from_url()`. ### Remediation Upgrade to urllib3 version 2.7.0 or later, in which sensitive headers are stripped from redirects followed by `HTTPConnection`. If upgrading is not immediately possible, avoid using this low-level redirect flow for cross-origin redirects. If appropriate for your use case, switch to `ProxyManager.request()`.

Affected Software

3 affected componentsFixes available
pip/urllib3>=1.23<2.7.0
2.7.0
Python urllib3>=1.23<2.7.0
Microsoft azl3 python-urllib3 2.0.7-4

Event History

May 11, 2026
Advisory Published
via GitHub·02:51 PM
Data Sourced
via GitHub·02:51 PM
DescriptionWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·03:20 PM
Data Sourced
via MITRE·03:20 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software
May 16, 2026
Data Sourced
via Microsoft·08:05 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:05 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-44431?

CVE-2026-44431 has a moderate severity level due to the risk of exposing sensitive headers in cross-origin requests.

2

How do I fix CVE-2026-44431?

To mitigate CVE-2026-44431, upgrade urllib3 to version 2.7.0 or later.

3

Which versions of urllib3 are affected by CVE-2026-44431?

CVE-2026-44431 affects urllib3 versions from 1.23 up to, but not including, 2.7.0.

4

What are the implications of CVE-2026-44431?

CVE-2026-44431 can lead to the unintended transmission of sensitive headers, potentially compromising user privacy and security.

5

Can CVE-2026-44431 impact my application?

Yes, CVE-2026-44431 may impact applications using urllib3 for HTTP requests that follow cross-origin redirects.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203