Skip to content
Cloud

CVE-2026-15183

9.2
Critical
EPSS 0.31%Patch availableJul 14, 2026

Input validation flaws in Snowflake Spark Connector allow credential theft and SQL injection.

common questions

Is CVE-2026-15183 being exploited?

Not confirmed. CVE-2026-15183 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.

How severe is CVE-2026-15183?

CVE-2026-15183 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-15183?

Yes. A fix has been recorded for CVE-2026-15183. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-15183 affect?

CVE-2026-15183 affects Snowflake Spark Connector (spark-snowflake) < 3.2.1, Apache Spark with shared Spark-SQL sessions, Snowflake accounts using connector. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15183?

Upgrade spark-snowflake to >=3.2.1, rotate OAuth creds, restrict shared Spark-SQL sessions, audit ingestion pipelines.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Snowflake Spark Connector (spark-snowflake) < 3.2.1Apache Spark with shared Spark-SQL sessionsSnowflake accounts using connector
impact

Attackers can exfiltrate OAuth client credentials, execute arbitrary SQL as the connector role, redirect COPY to attacker storage, and escalate privileges.

action required

Immediate action required

affected versions
Snowflake Snowflake Spark Connector
  • affected>= 0.1.0 and < 3.2.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free