CVE-2026-19553

SSLContext.wrap_bio() missing validation of server_hostname parameter

  • High 7.6

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.

Key facts

Published
30 Sep 2026
Last changed
10 Nov 2026
Assigned by
PSF
EPSS
0.547% likely to be exploited in the next 30 days, higher than 46.41% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.6CVSS 4.0, Highfrom the CNA (PSF)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Python Software FoundationCPython
  • Default status: unaffected
  • 0 up to but excluding 3.10.22 (affected)
  • 3.11.0 up to but excluding 3.11.17 (affected)
  • 3.12.0 up to but excluding 3.12.15 (affected)
  • 3.13.0 up to but excluding 3.13.16 (affected)
  • 3.14.0 up to but excluding 3.14.8 (affected)
  • 3.15.0a1 up to but excluding 3.15.0rc3 (affected)

Timeline

  1. 30 Sep 2026 Published

Weakness

References