Quick answers
- Is CVE-2026-15183 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15183 being exploited in the wild.
- How severe is CVE-2026-15183?
- Informational severity, with a CVSS score of 9.2, published 14 July 2026.
- Which products and versions are affected?
- Snowflake Spark Connector < 3.2.1.
- Is there a fix for CVE-2026-15183?
- A patch was published on 2026-07-08: Version 3.2.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-15183 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-15183?
- Check whether you run Snowflake Spark Connector at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Snowflake Spark Connector (spark-snowflake) prior to version 3.2.1 is affected by multiple input validation flaws including SQL Injection (CWE-89), Server-Side Request Forgery (CWE-918), and Confused Deputy (CWE-441) vulnerabilities. Attackers can exploit these by crafting malicious OAuth token request URLs, injecting SQL via staging options in shared Spark environments, or using runtime SET commands to override trusted catalog connection options. Successful exploitation allows for the exfiltration of OAuth client credentials, execution of arbitrary SQL under the connector's role, or redirection of COPY operations to attacker-controlled storage. The issues were addressed in version 3.2.1 by restricting the fallback catalog to immutable configurations, improving identifier quoting, and adding URL scheme/host validation.
Affected products
- Snowflake Snowflake Spark Connector (spark-snowflake) < 3.2.1
Timeline
- 2026-07-08: patched: Version 3.2.1 released
- 2026-07-14: advisory: NVD publication date