Fedora Account System
Red Hat Associate
Red Hat Customer
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.
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:84578 https://access.redhat.com/errata/RHSA-2026:84578
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:84577 https://access.redhat.com/errata/RHSA-2026:84577
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:85930 https://access.redhat.com/errata/RHSA-2026:85930
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:85929 https://access.redhat.com/errata/RHSA-2026:85929
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:90494 https://access.redhat.com/errata/RHSA-2026:90494
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:92474 https://access.redhat.com/errata/RHSA-2026:92474
This issue has been addressed in the following products: Red Hat Satellite 6.17 for RHEL 9 Via RHSA-2026:95656 https://access.redhat.com/errata/RHSA-2026:95656
This issue has been addressed in the following products: Red Hat Satellite 6.18 for RHEL 9 Via RHSA-2026:95657 https://access.redhat.com/errata/RHSA-2026:95657
This issue has been addressed in the following products: Red Hat Satellite 6.16 for RHEL 8 Red Hat Satellite 6.16 for RHEL 9 Via RHSA-2026:95655 https://access.redhat.com/errata/RHSA-2026:95655
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:98096 https://access.redhat.com/errata/RHSA-2026:98096
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions Via RHSA-2026:98097 https://access.redhat.com/errata/RHSA-2026:98097
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:98098 https://access.redhat.com/errata/RHSA-2026:98098
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions Via RHSA-2026:98125 https://access.redhat.com/errata/RHSA-2026:98125
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:98126 https://access.redhat.com/errata/RHSA-2026:98126
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:98122 https://access.redhat.com/errata/RHSA-2026:98122