dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15183

CRITICAL · 9.2 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Snowflake Spark Connector (spark-snowflake) versions before 3.2.1 contain multiple input validation vulnerabilities allowing OAuth client credential exfiltration via crafted token request URLs, arbitrary SQL execution through staging options in shared Spark environments, and redirection of COPY operations to attacker-controlled storage. Attackers can inject SQL via runtime SET commands in shared Spark-SQL sessions to compromise the SnowflakeFallbackCatalog's option map, executing under cluster admin JDBC credentials.

MitigationUpgrade spark-snowflake to version 3.2.1 or later. Avoid shared Spark environments, implement strict input validation on all user-supplied options, and restrict OAuth token endpoint access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify spark-snowflake connector version
    Locate the spark-snowflake connector JAR in your Spark cluster's classpath or dependencies list (commonly in /usr/spark/jars/, /opt/spark/jars/, or your project's Maven/Spark dependencies), then run 'jar manifest' or check your dependency manager for the version attribute
    Affected if The installed version is earlier than 3.2.1 (for example, 3.1.5, 3.0.6, 2.x.x)
  2. Confirm shared Spark environment usage
    Determine whether the Spark cluster is shared among multiple users or tenants, which is required for the attacker to exploit the vulnerability in the summary
    Affected if The connector runs in a multi-tenant or shared Spark environment where untrusted users can submit jobs
  3. Review staging options in COPY operations
    Inspect any Snowflake COPY INTO statements or DataFrame write operations using the connector that include staging options (STAGE_STORAGE_INTEGRATION, STAGE_COPY_OPTIONS, or custom stage parameters)
    Affected if Staging options are exposed to users or allow external URL configurations that could be tampered with
  4. Audit runtime SET command usage
    Search Spark application code, notebooks, or job configurations for calls to the connector's SET method or runtime configuration options that populate the SnowflakeFallbackCatalog's option map
    Affected if Runtime SET commands or dynamic option injection is used to configure the connector
  5. Check SnowflakeFallbackCatalog configuration
    Examine the connector's catalog configuration for SnowflakeFallbackCatalog settings and verify whether cluster admin JDBC credentials are used for execution
    Affected if SnowflakeFallbackCatalog is enabled and executes under elevated cluster admin credentials accessible to shared environment users

You are affected if the spark-snowflake connector version is before 3.2.1 AND the environment is a shared Spark cluster where users can access staging options or use runtime SET commands to inject SQL through the SnowflakeFallbackCatalog.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade spark-snowflake to version 3.2.1 or later. Avoid shared Spark environments, implement strict input validation on all user-supplied options, and restrict OAuth token endpoint access.

Recommended fix High confidence

spark-snowflake version 3.2.1

  1. Upgrade the spark-snowflake connector to version 3.2.1 or later in your project dependencies
  2. For Maven projects, update the dependency in pom.xml to <version>3.2.1</version> for artifact spark-snowflake
  3. For SBT projects, update the dependency to "net.snowflake:spark-snowflake_2.12:3.2.1" (or appropriate Scala version)
  4. For Gradle projects, update the dependency to implementation 'net.snowflake:spark-snowflake_2.12:3.2.1'
  5. Rebuild and redeploy your Spark application with the updated connector version
  6. Verify the upgrade does not introduce regressions in your data pipelines that use OAuth authentication, COPY operations, or staging options

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
46.0 hours of engineering $8,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15183 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data