CVE-2026-19553

High

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.

SeverityHigh
CVSS7.6
Exploit probability—
ProductCPython
PublishedSep 30, 2026
First seenSep 30, 2026
Weakness typeCWE-297CWE-297

How to fix

Affected products

ProductAffected versionsFixed in
Python Software Foundation CPythonv < 3.10.22, 3.11.0 ≤ v < 3.11.17, 3.12.0 ≤ v < 3.12.15, 3.13.0 ≤ v < 3.13.16, 3.14.0 ≤ v < 3.14.8, 3.15.0a1 ≤ v < 3.15.0rc33.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8, 3.15.0rc3

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.