Bug 2544127 (CVE-2026-19553)

Summary: CVE-2026-19553 python: python: Certificate verification bypass via missing server_hostname validation in SSLContext.wrap_bio()
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: bbrownin, cahl, dfreiber, dkeler, drow, dschmidt, gbenhaim, jburrell, jlanda, kshier, ljawale, msilmser, niyer, rbobbitt, rhel-process-autobot, simaishi, stcannon, suppawar, thason, twaugh, vkumar, watson-tool-maintainers, yguenane
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Python. When establishing secure connections using the SSLContext.wrap_bio() function with hostname checking enabled, the module fails to validate that a target server hostname is supplied. Because of this missing check, certificate hostname verification is silently skipped rather than triggering an error. A remote man-in-the-middle attacker could exploit this defect to spoof trusted endpoints and intercept or tamper with sensitive encrypted traffic.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2546325, 2546327, 2546328, 2546329, 2546318, 2546319, 2546320, 2546321, 2546322, 2546323, 2546324, 2546326    
Bug Blocks:    

Description OSIDB Bzimport 2026-09-30 16:42:19 UTC
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.

Comment 1 Jon Orris 2026-10-07 03:09:47 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:77028 https://access.redhat.com/errata/RHSA-2026:77028

Comment 2 Jon Orris 2026-10-08 08:15:10 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:77021 https://access.redhat.com/errata/RHSA-2026:77021

Comment 3 Jon Orris 2026-10-08 08:17:34 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:77017 https://access.redhat.com/errata/RHSA-2026:77017

Comment 4 Jon Orris 2026-10-08 08:40:31 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:77018 https://access.redhat.com/errata/RHSA-2026:77018

Comment 5 Jon Orris 2026-10-08 09:32:15 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:77020 https://access.redhat.com/errata/RHSA-2026:77020

Comment 6 Jon Orris 2026-10-19 16:29:58 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:85239 https://access.redhat.com/errata/RHSA-2026:85239

Comment 7 Jon Orris 2026-10-26 04:25:32 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:89742 https://access.redhat.com/errata/RHSA-2026:89742

Comment 9 Jon Orris 2026-11-03 08:38:05 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On

Via RHSA-2026:94443 https://access.redhat.com/errata/RHSA-2026:94443

Comment 10 Jon Orris 2026-11-04 10:37:23 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

Via RHSA-2026:95082 https://access.redhat.com/errata/RHSA-2026:95082

Comment 11 errata-xmlrpc 2026-11-11 12:06:42 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:98511 https://access.redhat.com/errata/RHSA-2026:98511