CVE-2026-19553: ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if
Source GCVE Database
Not known to be exploited · CVSS 7.6 High · fixed in 3.15.0rc3 : patch CPython soon.
Data as of 10 Nov 2026, 16:36 UTC
Thin evidence
One scorer or none| CNA (PSF) | CVSS 4.0 | 7.6 |
|---|
- Patch
- Available – fixed in 3.15.0rc3, 3.14.8, 3.13.16 +3
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 10 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if ssl.SSLContext.check_hostname was set. Due to a missing parameter check in SSLObject, if the server_hostname argument isn't supplied then hostname verification would be silently skipped. This defect could lead to programs where certificate hostname verification *appeared* to be succeeding with SSLContext.check_hostname = True and no ValueError being raised due to misconfiguration. If the program passes a server_hostname value that isn't an empty string or None to any of these APIs then certificate hostname verification proceeds as expected and the program is not affected by this vulnerability. Mitigating this vulnerability doesn't require updating Python or applying the patch. To mitigate, pass a valid non-None and non-empty server_hostname value to SSLContext.wrap_bio(), asyncio.create_connection(), or asyncio.loop.start_tls() and certificate hostname verification will proceed as expected. Upgrading to the latest version of Python or applying the patch only changes the behavior from silently skipping hostname verification to raising a ValueError, similar to SSLContext.wrap_socket(), when server_hostname isn't supplied.
References
- nvd.nist.gov/vuln/detail/CVE-2026-19553 (opens in a new tab)
- github.com/python/cpython/issues/156793 (opens in a new tab)
- github.com/python/cpython/pull/158503 (opens in a new tab)
- github.com/python/cpython/commit/1697ea386c707142555d98a1263176bbbc014a96 (opens in a new tab)
- github.com/python/cpython/commit/5867d4e4ae6d1062352baf6b497a4026e8578ccf (opens in a new tab)
- github.com/python/cpython/commit/641390146a16a38e6701923f4ee4f1940ae77082 (opens in a new tab)
- github.com/python/cpython/commit/869069d52ce0efab2f8c38197e92cdaaa312f1ed (opens in a new tab)
- github.com/python/cpython/commit/966bf426d0b6c31c1b0a255ff14a17143a466ced (opens in a new tab)
- github.com/python/cpython/commit/bdebbf9b366ec91e9cd9daa0b3510c9e84b60b80 (opens in a new tab)
- github.com/python/cpython/commit/f4e43ba525187282f2011da0e6ffc0d2b08d8062 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)
- mail.python.org/archives/list/security-announce@python.org/thread/QNZRG3YOAMTHDCMVCICXGY6YEFPY2VDL (opens in a new tab)
- openwall.com/lists/oss-security/2026/09/30/16 (opens in a new tab)