CVE-2026-97687: python-urllib3 security update
Affects python-urllib3Source GCVE Database
Not known to be exploited · CVSS 7.6 High : upgrade to 1.26.18-11.oe2403sp4 soon.
Data as of 29 Oct 2026, 10:48 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.26.18-11.oe2403sp4
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:XExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade python-urllib3 to 1.26.18-11.oe2403sp4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
openEuler 24.03-LTS-SP4python-urllib3pkg:rpm/openEuler/python-urllib3&distro=openEuler-24.03-LTS-SP4Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade python-urllib3 to version 1.26.18-11.oe2403sp4 or later, where this issue is fixed. Since a patch is available, applying the official fix is the recommended mitigation.
Description
A vulnerability in python-urllib3 versions prior to 1.26.18-11.oe2403sp4 allows HTTPS proxy TLS settings to be incorrectly shared with target-server TLS settings. This can lead to an attacker impersonating the HTTPS proxy and intercepting or modifying forwarded traffic. The issue is fixed in version 1.26.18-11.oe2403sp4.