Advisory

PYSEC-2026-3920

Also known as: CVE-2026-15925, GHSA-5cc2-282f-jjq2

Summary

Snowflake Connector for Python improperly verifies TLS hostnames

Details

Improper TLS hostname verification in Snowflake Connector for Python versions prior to 4.7.1 and 3.18.1 may have allowed a network-positioned attacker to bypass certificate hostname validation on HTTPS connections made by the connector. An attacker with on-path network access could exploit this by intercepting or redirecting network traffic and presenting a certificate signed by any trusted CA for any domain, causing the connector to accept connections without validating that the certificate matched the requested hostname. Successful exploitation requires an on-path traffic interception capability (e.g. ARP/DNS poisoning, rogue access point, BGP hijacking, or malicious proxy/exit node). This vulnerability may have exposed credentials, query data, and staged file contents to interception and tampering, and may have enabled the attacker to issue arbitrary SQL within the context of the victim's connector session. Impact is limited by the privileges of the affected Snowflake role. The fix is available in Snowflake Connector for Python versions 4.7.1 and 3.18.1. Users must manually upgrade.

Severity

Not rated by the source.

Dates

Published
2026-09-10 09:44 UTC
Modified
2026-09-10 12:15 UTC

Affected packages and fixes

snowflake-connector-python

PyPI · All systems

Affected

  • introduced 0, fixed 3.18.1, introduced 4.0.0, fixed 4.7.1 (ecosystem)

Fixed versions

3.18.1, 4.7.1

Fix

  • Fixed version 3.18.1
    pip install --upgrade snowflake-connector-python==3.18.1
  • Fixed version 4.7.1
    pip install --upgrade snowflake-connector-python==4.7.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences