Skip to content
Heist/ feed
Back to feed
Unrated

CVE-2026-97687 affecting package tensorflow 2.16.1-11

Type: advisorySources: OSV

urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0.

Products
tensorflow
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-97687
Confirmed fixed CVEs
Not specified
Updated in this feed
30 Oct 2026, 14:05 UTC · Revision 1

Source evidence

CVE-2026-97687 affecting package tensorflow 2.16.1-11

core-osv · Original source

Published 29 Sept 2026, 16:17 UTC

urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0.

osv:AZL-105909

tensorflow

Fixed versions: Not specified

Complete source record
{
  "id": "b86b1791aec3a74bb6178ac9f97a3e5622c3913bfd280ed0881d521a2d327fe7",
  "url": "https://osv.dev/vulnerability/AZL-105909",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "CVE-2026-97687 affecting package tensorflow 2.16.1-11",
    "summary": "urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0.",
    "evidence": "osv:AZL-105909",
    "products": [
      {
        "name": {
          "value": "tensorflow",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "AZL-105909",
      "aliases": [
        "AZL-105909"
      ],
      "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-105909.json"
          }
        }
      ],
      "modified": "2026-10-15T05:37:09Z",
      "provider": "osv",
      "upstream": [
        "CVE-2026-97687"
      ],
      "references": [
        "https://nvd.nist.gov/vuln/detail/CVE-2026-97687"
      ]
    },
    "related_cves": [
      {
        "value": "CVE-2026-97687",
        "evidence": "/upstream"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 321399,
  "published_at": "2026-09-29T16:17:18+00:00"
}