Skip to main content
VulnerabilityPublished Updated

CVE-2026-19553: ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-19553· High 7.6

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

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PSF)CVSS 4.07.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Python Software FoundationCPythonAffected
  • >=3.15.0a1 <3.15.0rc3
Fixed in
  • 3.15.0rc3
Python Software FoundationCPythonAffected
  • >=3.14.0 <3.14.8
Fixed in
  • 3.14.8
Python Software FoundationCPythonAffected
  • >=3.13.0 <3.13.16
Fixed in
  • 3.13.16
Python Software FoundationCPythonAffected
  • >=3.12.0 <3.12.15
Fixed in
  • 3.12.15
Python Software FoundationCPythonAffected
  • >=3.11.0 <3.11.17
Fixed in
  • 3.11.17
Python Software FoundationCPythonAffected
  • <3.10.22
Fixed in
  • 3.10.22

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

Community reviews

Loading reviews…