PT-2026-109072 · Azure Linux · Python-Urllib3
Published
2026-09-29
·
Updated
2026-09-29
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy ssl context, proxy assert hostname, proxy assert fingerprint, ssl context, cert reqs, verify mode, use forwarding for https=True, and CERT NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert reqs=CERT NONE can overwrite proxy ssl context.verify mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Python-Urllib3