CVE-2026-15925

CRITICALPre-NVD 9.29.2—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
9.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.2
EG Score
9.2(medium)
EPSS
7.5%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 16, 2026

Advisory Details (1)

Auto-updated Jul 16, 2026
Patch available. Sources: github_release.
github_release Patch Available

4.7.1

Patch available: snowflakedb/snowflake-connector-python v4.7.1

https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v4.7.1

Vendor Advisories for CVE-2026-15925(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 06:12 UTCGHSA enrichment
  8. 2026-07-17 02:14 UTCGHSA enrichment
  9. 2026-07-16 22:15 UTCGHSA enrichment
  10. 2026-07-16 18:16 UTCGHSA enrichment
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-16 14:15 UTCGHSA enrichment
  13. 2026-07-16 10:17 UTCGHSA enrichment
  14. 2026-07-16 06:18 UTCEG score recompute
  15. 2026-07-16 06:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15925?
CVE-2026-15925 is a critical vulnerability published on July 16, 2026. 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…
When was CVE-2026-15925 disclosed?
CVE-2026-15925 was first published in the National Vulnerability Database on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15925 actively exploited?
CVE-2026-15925 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15925?
CVE-2026-15925 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2026-15925?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15925, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15925

Explore →

Is Your Infrastructure Affected by CVE-2026-15925?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs