CVE-2026-19553 affecting package tensorflow 2.16.1-11
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.
- Products
- tensorflow
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-19553
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 14:05 UTC · Revision 1
Source evidence
CVE-2026-19553 affecting package tensorflow 2.16.1-11
core-osv · Original sourcePublished 30 Sept 2026, 17:16 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.
osv:AZL-105918
tensorflow
Fixed versions: Not specified
Complete source record
{
"id": "674d8614bd7111310e37e0024e73e941606eadc8cdd9f3a8f648f548190e7629",
"url": "https://osv.dev/vulnerability/AZL-105918",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2026-19553 affecting package tensorflow 2.16.1-11",
"summary": "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.",
"evidence": "osv:AZL-105918",
"products": [
{
"name": {
"value": "tensorflow",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "AZL-105918",
"aliases": [
"AZL-105918"
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.16.1-11"
}
]
}
],
"package": {
"name": "tensorflow",
"purl": "pkg:rpm/azure-linux/tensorflow",
"ecosystem": "Azure Linux:3"
},
"database_specific": {
"source": "https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-105918.json"
}
}
],
"modified": "2026-10-15T05:37:09Z",
"provider": "osv",
"upstream": [
"CVE-2026-19553"
],
"references": [
"https://nvd.nist.gov/vuln/detail/CVE-2026-19553"
]
},
"related_cves": [
{
"value": "CVE-2026-19553",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 321402,
"published_at": "2026-09-30T17:16:45+00:00"
}