一、漏洞信息
漏洞编号：CVE-2026-97687
漏洞归属组件：python-urllib3
漏洞归属的版本：1.24.3,1.25.9,1.26.12,1.26.16,1.26.18,1.26.3,1.26.7,2.3.0
CVSS评分：
BaseScore：7.6 High
Vector：CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
漏洞简述：
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.
漏洞公开时间：2026-09-30 00:17:18
漏洞创建时间：2026-10-14 06:37:49
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-97687

漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息：

二、漏洞分析结构反馈
影响性分析说明：
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.
openEuler评分：
7.6
Vector：CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
受影响版本排查(受影响/不受影响)：
1.master(2.3.0):受影响
2.openEuler-20.03-LTS-SP4(1.25.9):不受影响
3.openEuler-22.03-LTS-SP4(1.26.12):受影响
4.openEuler-24.03-LTS-Next(1.26.18):受影响
5.openEuler-24.03-LTS-SP1(1.26.18):受影响
6.openEuler-24.03-LTS-SP3(1.26.18):受影响
7.openEuler-24.03-LTS-SP4(1.26.18):受影响

修复是否涉及abi变化(是/否)：
1.master(2.3.0):否
2.openEuler-20.03-LTS-SP4(1.25.9):否
3.openEuler-22.03-LTS-SP4(1.26.12):否
4.openEuler-24.03-LTS-Next(1.26.18):否
5.openEuler-24.03-LTS-SP1(1.26.18):否
6.openEuler-24.03-LTS-SP3(1.26.18):否
7.openEuler-24.03-LTS-SP4(1.26.18):否

原因说明：
1.master(2.3.0):正常修复
2.openEuler-20.03-LTS-SP4(1.25.9):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4(1.26.12):正常修复
4.openEuler-24.03-LTS-Next(1.26.18):正常修复
5.openEuler-24.03-LTS-SP1(1.26.18):正常修复
6.openEuler-24.03-LTS-SP3(1.26.18):正常修复
7.openEuler-24.03-LTS-SP4(1.26.18):正常修复