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: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | 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
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 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 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 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 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 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 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 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 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 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 |