OCTOBER 8, 2026
Live Feed
Back to database
Case File

CVE-2026-19553

HIGH · CVSS 7.6 EPSS 0.40% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-30 · Last synced 2026-10-08

CyberRota Analysis

AI-Generated

The vulnerability affects the SSLContext in Python, where the server_hostname argument is not enforced when SSLContext.check_hostname is set to True, potentially allowing hostname verification to be bypassed without any error. This could mislead applications into believing that certificate verification is successful, posing a significant security risk. Organizations using affected Python versions, especially those handling sensitive data or relying on secure communications, should prioritize implementing a fix by ensuring a valid server_hostname is provided to relevant SSL APIs.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-19553
Severity
HIGH
CVSS
7.6
EPSS
0.40%

Original NVD 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.