Multiple input validation vulnerabilities in the Snowflake Spark Connector (spark-snowflake) versions prior to 3.2.1 can allow attackers to exfiltrate OAuth client credentials, execute arbitrary SQL with the connector's Snowflake role, or redirect COPY operations to attacker-controlled storage. An attacker could exploit these vulnerabilities by supplying a crafted OAuth token request URL, placing malicious files in an ingestion pipeline, injecting SQL via staging options in a shared Spark environment , or issuing runtime SET commands in a shared Spark-SQL session to inject arbitrary SQL into the SnowflakeFallbackCatalog's option map, which executes under the cluster admin's JDBC credentials. Successful exploitation may result in credential theft, unauthorized access to Snowflake account data, or privilege escalation within connected infrastructure.
CVE-2026-15183
This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.2
- EG Score
- 9.2(medium)
- EPSS
- 10.9%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (1)
Auto-updated Jul 14, 2026Snowflake Connector for Spark release notes for 2026 | Snowflake Documentation
https://docs.snowflake.com/en/release-notes/clients-drivers/spark-connector-2026Vendor Advisories for CVE-2026-15183(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 22× 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.
- 2026-07-15 23:03 UTCEG score recompute
- 2026-07-15 23:03 UTCGHSA enrichment
- 2026-07-15 18:50 UTCEG score recompute
- 2026-07-15 18:50 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 14:38 UTCEG score recompute
- 2026-07-15 14:38 UTCGHSA enrichment
- 2026-07-15 10:24 UTCEG score recompute
- 2026-07-15 10:24 UTCGHSA enrichment
- 2026-07-15 06:11 UTCEG score recompute
- 2026-07-15 06:11 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:59 UTCEG score recompute
- 2026-07-15 01:59 UTCGHSA enrichment
- 2026-07-14 21:47 UTCEG score recompute
- 2026-07-14 21:47 UTCGHSA enrichment
- 2026-07-14 17:35 UTCEG score recompute
- 2026-07-14 17:35 UTCGHSA enrichment
- 2026-07-14 13:23 UTCEG score recompute
- 2026-07-14 13:23 UTCGHSA enrichment
- 2026-07-14 09:10 UTCEG score recompute
- 2026-07-14 09:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-89 · CWE-918
Frequently asked(5)
What is CVE-2026-15183?
When was CVE-2026-15183 disclosed?
Is CVE-2026-15183 actively exploited?
What is the CVSS score of CVE-2026-15183?
How do I remediate CVE-2026-15183?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15183
Is Your Infrastructure Affected by CVE-2026-15183?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.