Python Software Foundation · Python (CPython) · published 2026-09-30

CVE-2026-19553SSLContext.wrap_bio() missing validation of server_hostname parameter

Routine No exploitation evidence; EPSS 0.5%.

CVE-2026-19553 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 46% of all CVEs. This Python (CPython) vulnerability: CVSS 7.6 (v4.0), a successful attack gives total control of the component. Fixed upstream in Python (CPython) 3.14.8, 3.13.16, 3.12.15, 3.11.17 (+1 more); patched packages are out for Debian; Ubuntu still has unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Python (CPython) 3.14.8, 3.13.16, 3.12.15, 3.11.17, 3.10.22.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixiepypy3Won’t fix
13 trixiepython3.13Won’t fix
12 bookwormpypy3Won’t fix
12 bookwormpython3.11Fixed in 3.11.2-6+deb12u9
Ubuntu26.04 LTSpython3.14No fix yet
24.04 LTSpython3.12No fix yet
22.04 LTSpython3.10No fix yet
Red Hat Enterprise Linux (+11 more packages)RHEL 9python3.11Won’t fix
RHEL 8python3.11Won’t fix

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    Language runtimePython (CPython)

    Python (CPython) security releases: 3.14.8, 3.13.16, 3.12.15, 3.11.17, 3.10.22

    Upgrade to 3.14.83.13.163.12.153.11.173.10.22

    Why: CVE-2026-15806: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.5% (47th pct)FIRST EPSS v2026.06.15
CVSS base score7.6 (v4.0)
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
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →