Поиск уязвимостей
Количество 25
Количество 25
GHSA-xx9w-qm94-hghj
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....
CVE-2026-19553
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. Upgra...
CVE-2026-19553
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. Upgra...
CVE-2026-19553
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. Up
CVE-2026-19553
SSLContext.wrap_bio() missing validation of server_hostname parameter
CVE-2026-19553
ssl.SSLContext.wrap_bio() didn't require the server_hostname argument ...
RLSA-2026:77028
Important: python3.12 security update
RLSA-2026:77021
Important: python3.14 security update
RLSA-2026:77020
Important: python3.12 security update
RLSA-2026:77018
Important: python3.14 security update
RLSA-2026:77017
Important: python3.12 security update
ELSA-2026-77028
ELSA-2026-77028: python3.12 security update (IMPORTANT)
ELSA-2026-77021
ELSA-2026-77021: python3.14 security update (IMPORTANT)
ELSA-2026-77020
ELSA-2026-77020: python3.12 security update (IMPORTANT)
ELSA-2026-77018
ELSA-2026-77018: python3.14 security update (IMPORTANT)
ELSA-2026-77017
ELSA-2026-77017: python3.12 security update (IMPORTANT)
SUSE-SU-2026:4659-1
Security update for python312
RLSA-2026:89742
Important: python3.9 security update
RLSA-2026:85239
Important: python3 security update
ELSA-2026-89742
ELSA-2026-89742: python3.9 security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-xx9w-qm94-hghj 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.... | 1% Низкий | около 2 месяцев назад | ||
CVE-2026-19553 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. Upgra... | 1% Низкий | около 2 месяцев назад | ||
CVE-2026-19553 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. Upgra... | CVSS3: 7.4 | 1% Низкий | около 2 месяцев назад | |
CVE-2026-19553 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. Up | 1% Низкий | около 2 месяцев назад | ||
CVE-2026-19553 SSLContext.wrap_bio() missing validation of server_hostname parameter | 1% Низкий | около 1 месяца назад | ||
CVE-2026-19553 ssl.SSLContext.wrap_bio() didn't require the server_hostname argument ... | 1% Низкий | около 2 месяцев назад | ||
RLSA-2026:77028 Important: python3.12 security update | около 1 месяца назад | |||
RLSA-2026:77021 Important: python3.14 security update | около 1 месяца назад | |||
RLSA-2026:77020 Important: python3.12 security update | около 1 месяца назад | |||
RLSA-2026:77018 Important: python3.14 security update | около 1 месяца назад | |||
RLSA-2026:77017 Important: python3.12 security update | около 1 месяца назад | |||
ELSA-2026-77028 ELSA-2026-77028: python3.12 security update (IMPORTANT) | около 1 месяца назад | |||
ELSA-2026-77021 ELSA-2026-77021: python3.14 security update (IMPORTANT) | около 1 месяца назад | |||
ELSA-2026-77020 ELSA-2026-77020: python3.12 security update (IMPORTANT) | около 1 месяца назад | |||
ELSA-2026-77018 ELSA-2026-77018: python3.14 security update (IMPORTANT) | около 1 месяца назад | |||
ELSA-2026-77017 ELSA-2026-77017: python3.12 security update (IMPORTANT) | около 1 месяца назад | |||
SUSE-SU-2026:4659-1 Security update for python312 | около 1 месяца назад | |||
RLSA-2026:89742 Important: python3.9 security update | 22 дня назад | |||
RLSA-2026:85239 Important: python3 security update | 28 дней назад | |||
ELSA-2026-89742 ELSA-2026-89742: python3.9 security update (IMPORTANT) | 24 дня назад |
Уязвимостей на страницу