CVE-2026-15925
Last modified
CVE-2026-15925 is a critical-severity vulnerability rated 9.2/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Snowflake | Snowflake Connector for Python | >= 3.17.4, < 3.18.1; >= 4.0.0, < 4.7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-15925?
How severe is CVE-2026-15925?
How do I fix CVE-2026-15925?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-15918VikAppointments Service Booking Calendar wordpress plugin is…7.5
- CVE-2026-1592Foxit PDF Editor Cloud (pdfonline) contains a stored cross-s…5.4
- CVE-2026-15920An issue was discovered in Django 5.2 before 5.2.17 and 6.0 …6.1
- CVE-2026-15921Node Version Manager (nvm) is a POSIX-compliant shell functi…3.1
- CVE-2026-15923The Zephyr SDIO subsystem function sdio_io_rw_extended_helpe…4.6
- CVE-2026-15924Zephyr's TLS socket layer in subsys/net/lib/sockets/sockets_…5.9
- CVE-2026-15926Rejected reason: Red Hat Product Security has determined tha…
- CVE-2026-15927A flaw was found in Red Hat Quay's repository-level mirror c…6.8
- CVE-2026-15928XMLRPC-C Library versions 1.07 through 1.67.01 are vulnerabl…8.2
- CVE-2026-15929Improper neutralization of special elements used in an SQL c…7.1
- CVE-2026-1593A weakness has been identified in itsourcecode Society Manag…9.8
- CVE-2026-15930The Simple Membership WordPress plugin before 4.7.8 does not…9.4
Are you affected by CVE-2026-15925?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
