Furthermore, the library performs in-place mutation of SSL context objects when certificate verification is disabled for a target (e.g., using cert_reqs="CERT_NONE"). Because this mutation is applied to the context object directly, these changes can persist and be applied to subsequent connections that reuse the same context, effectively disabling certificate verification for the proxy connection as well. An attacker capable of intercepting traffic to the HTTPS proxy can leverage these misconfigurations to impersonate the proxy, intercepting sensitive data, authentication tokens, or observing forwarded request bodies.

Impact

Successful exploitation allows an attacker to perform man-in-the-middle attacks on HTTPS traffic forwarded through a proxy. This exposes sensitive information, including request/response bodies, credentials, and authentication tokens. Additionally, a client certificate intended for a target server might be improperly presented to the proxy or an attacker, leading to the disclosure of the client's identity and providing proof of possession of the client's private key.

Recommendation

Prioritize the upgrade of all applications utilizing the affected versions of urllib3.

• Upgrade to urllib3 2.8.0 or later to ensure proper isolation of proxy and target SSL contexts.
• Update codebases to use the proxy_ssl_context parameter for configuring TLS on HTTPS forwarding proxies rather than relying on global or target-specific ssl_context objects.
• Review applications using use_forwarding_for_https=True to ensure they are not passing a shared ssl_context that may be mutated in-place during target-specific certificate verification.
• Monitor for FutureWarning messages generated by urllib3 2.8.0, which indicate legacy configurations that will be deprecated and produce errors in urllib3 3.0.