Affects Snowflake's widely used Python connector; enables MitM data theft and arbitrary SQL, posing broad cross-industry risk to enterprise cloud data access.
CVE-2026-15925
TLS hostname verification bypass in Snowflake Python connector enabling MitM attacks
Is CVE-2026-15925 being exploited?
Not confirmed. CVE-2026-15925 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-15925?
CVE-2026-15925 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15925?
Yes. A fix has been recorded for CVE-2026-15925. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15925 affect?
CVE-2026-15925 affects Snowflake Connector for Python < 4.7.1, Applications using that connector. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15925?
Upgrade to Snowflake Connector for Python 4.7.1, rotate credentials, and audit logs/network access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
On-path attacker can bypass hostname validation to intercept/modify queries, steal credentials/staged files, and run arbitrary SQL as the connector role.
Immediate action required
- affected>= 3.17.4 and < 3.18.1
- affected>= 4.0.0 and < 4.7.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.