CVE-2026-19553: python3 security update
Affects python3Source GCVE Database
Not known to be exploited · CVSS 7.6 High : upgrade to 3.11.6-46.oe2403sp4 soon.
Data as of 29 Oct 2026, 11:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.11.6-46.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:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 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 python3 to 3.11.6-46.oe2403sp4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
openEuler 24.03-LTS-SP4python3pkg:rpm/openEuler/python3&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
To mitigate this vulnerability without updating Python, ensure that a valid, non-None, and non-empty server_hostname argument is passed to SSLContext.wrap_bio(), asyncio.create_connection(), or asyncio.loop.start_tls(). This will enforce proper hostname verification. Applying the official patch or upgrading to Python version 3.11.6-46.oe2403sp4 or later changes the behavior to raise a ValueError when server_hostname is omitted, preventing silent verification bypass.
Description
A security vulnerability in Python's ssl module (CVE-2026-19553) affects the SSLContext.wrap_bio() method where the server_hostname argument was not properly validated. If server_hostname is not supplied, hostname verification is silently skipped despite SSLContext.check_hostname being set to True. This could cause programs to mistakenly believe certificate hostname verification succeeded. Passing a valid non-empty server_hostname prevents the issue. The vulnerability is fixed in Python version 3.11.6-46.oe2403sp4.