CVE-2026-19553: python3 security update
Affects python3Source GCVE Database
Not known to be exploited · CVSS 7.6 High : upgrade to 3.11.6-44.oe2403sp1 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-44.oe2403sp1
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-44.oe2403sp1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
openEuler 24.03-LTS-SP1python3pkg:rpm/openEuler/python3&distro=openEuler-24.03-LTS-SP1Other 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
A fix is available in Python version 3.11.6-44.oe2403sp1. Users should upgrade to this version or later to ensure the vulnerability is patched. Alternatively, without upgrading, developers can mitigate the issue by always passing a valid, non-None, and non-empty server_hostname argument to ssl.SSLContext.wrap_bio(), asyncio.create_connection(), or asyncio.loop.start_tls() to enforce hostname verification. This mitigation does not require a Python update.
Description
A vulnerability in Python's ssl.SSLContext.wrap_bio() method allows silent skipping of certificate hostname verification when the server_hostname argument is not provided, despite SSLContext.check_hostname being set to True. This can cause programs to mistakenly believe hostname verification succeeded, potentially weakening SSL/TLS security. The issue affects Python versions prior to 3.11.6-44.oe2403sp1. Mitigation can be achieved by passing a valid non-empty server_hostname parameter to relevant APIs. The vulnerability is fixed in Python 3.11.6-44.oe2403sp1, where missing server_hostname causes a ValueError instead of silent skipping.