Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v3.18.1
- https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v4.7.1
FAQ
What is CVE-2026-15925?
CVE-2026-15925 is a documented vulnerability. 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 HTTP...
How severe is CVE-2026-15925?
CVSS scoring is not yet available for CVE-2026-15925. Check NVD for updates.
Is there a patch for CVE-2026-15925?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.