Servers and applications
CVE-2026-19553
SSLContext.wrap_bio() missing validation of server_hostname parameter
- Severity
- High 7.6
- Published
- 30 Sept 2026
- Last changed
- 10 Nov 2026
- Added to UpHeron
- 10 Nov 2026
- Fixed in
- 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8, 3.15.0rc3
- Exploit chance
- 0.5% in the next 30 daysHigher than 46% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-297
- Attack
- Over the network · Only under certain conditions · No login needed · Needs someone to view a page or file
- Attacker can
- Read data · Change data
- CVSS vector
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- Sources
- CVE Program
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.
Affected software
| Software | Affected versions |
|---|---|
PythonServers and applications · cna:python software foundation|cpython |
|
About Python
general-purpose programming language
- Share of websites with a known server-side language
- 1.2%W3Techs, Nov 2026
- Developers who used it in the past year
- 57.9%Stack Overflow Developer Survey 2025, 2025
- Docker Hub pulls
- 9,640,071,763Docker Hub, 15 Nov 2026
- GitHub stars
- 78,222GitHub, 15 Nov 2026
- Forks
- 36,604GitHub, 15 Nov 2026
- Developer
- Python Software FoundationWikidata
- License
- Python Software Foundation LicenseWikidata
- Written in
- Python, CWikidata
- First released
- 20 Feb 1991Wikidata
- First published on GitHub
- 10 Feb 2017GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 3.15 | 3.15.2 | Until 31 Oct 2031 |
| 3.14 | 3.14.10 | Until 31 Oct 2030 |
| 3.13 | 3.13.18 | Until 31 Oct 2029 |
| 3.12 | 3.12.16 | Until 31 Oct 2028 |
| 3.11 | 3.11.18 | Until 31 Oct 2027 |
| 3.10 | 3.10.22 | Ended 1 Oct 2026 |
From endoflife.date.
Vulnerabilities in Python
- In our list
- 159
- Published in the last 12 months
- 33
- Critical, last 12 months
- 2
- High, last 12 months
- 5
- Known exploited
- 0
- CVE-2026-16052Cookie Attribute Injection via Unescaped Semicolons in http.cookies.MorselLow 2.3 12 Nov 2026
- CVE-2026-115559imaplib STARTTLS serves plaintext bytes buffered before the handshake as if they came over TLSMedium 6.3 10 Nov 2026
- CVE-2026-115791Prevent shadowing stdlib in gzip/tarfile/zipfile CLI during extractionMedium 5.3 10 Nov 2026
- CVE-2026-124249`http.cookiejar` applies expired `Set-Cookie` to cookie store before policy validationMedium 6.3 9 Nov 2026
- CVE-2026-19552ssl.get_server_certificate(addr, ca_certs=...) verifies the chain but never the identityUnrated 9 Nov 2026
- CVE-2026-119170Regression in FIPS enforcement of hash algorithms affecting only Python 3.14.10High 8.2 6 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-19553