Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Shared-session access to submit SET/staging options implies PR:L, and the required preconditions plus non-trivial injection path justify AC:H; full C/I/A impact via admin-role SQL execution.
Primary rating from Vendor (SNOWFLAKE).
CVSS VectorVendor: SNOWFLAKE
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
SQL injection and input-validation weaknesses in the Snowflake Spark Connector (spark-snowflake) before version 3.2.1 let attackers exfiltrate OAuth client credentials, run arbitrary SQL under the connector's Snowflake role, and redirect COPY data-loading operations to attacker-controlled storage. Reported by Snowflake, the flaws are most dangerous in shared/multi-tenant Spark clusters where injected SQL executes with the cluster admin's JDBC credentials, enabling credential theft and privilege escalation. Rated CVSS 4.0 9.2 (Critical); no public exploit identified at time of analysis.
Technical ContextAI
The Snowflake Spark Connector (spark-snowflake) is a JVM data-integration library that bridges Apache Spark and the Snowflake data cloud, using JDBC plus staged COPY INTO operations to move data in bulk and OAuth for authentication. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), manifesting through several unvalidated inputs: OAuth token-request URLs, staging/COPY options, and connector option maps that flow into the SnowflakeFallbackCatalog. Runtime Spark-SQL SET commands and staging options are incorporated into that option map without sanitization, so attacker-controlled strings are concatenated into SQL executed over the cluster's shared JDBC session, and COPY targets can be re-pointed to arbitrary storage locations.
RemediationAI
Upgrade the Snowflake Spark Connector to version 3.2.1 or later, which is the primary fix; consult the vendor release notes at https://docs.snowflake.com/en/release-notes/clients-drivers/spark-connector-2026 for the exact patched artifact and coordinates. Until you can upgrade, reduce exposure by not sharing a single Spark or Spark-SQL session across untrusted tenants or users (isolate workloads into per-tenant clusters), which removes the runtime-SET and staging-option injection paths at the cost of higher infrastructure overhead. Additionally, restrict who can supply connector options, staging options, and OAuth token-request URLs; run the connector's JDBC session under a least-privilege Snowflake role rather than a cluster-admin role to limit blast radius; and lock COPY operations to an allowlist of trusted, validated storage stages/locations to blunt redirection to attacker-controlled storage. These controls narrow but do not fully close the injection surface, so patching remains the definitive remedy.
Same weakness CWE-89 – SQL Injection
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-43644
GHSA-33r9-fx8q-w69h