External risk intelligence

Snowflake Snowpark Python SDK SQL Injection Vulnerabilities

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-15062

This vulnerability exists within a Python SDK used by developers for data processing tasks. It requires a local or integrated environment where users are already authenticated to interact with the database SDK, rather than serving as a public-facing network service or internet gateway.

SQL Injection

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A recent advisory highlights SQL injection vulnerabilities within the Snowflake Snowpark Python SDK. These issues could allow authenticated users with low privileges to execute unauthorized SQL commands, potentially leading to data exfiltration or compromise of sensitive account information. The primary concern at this time is to determine if our environment utilizes the affected SDK and if any exposure exists.

Authenticated users can run unauthorized SQL commands.
Data compromise and exfiltration are possible risks.
Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with existing low-privilege access to the Snowflake Snowpark Python SDK could exploit these SQL injection vulnerabilities. By carefully crafting input for specific SDK functions, such as DataFrameReader.dbapi(), DataFrameWriter write methods, or DataFrame.to_csv(), an attacker could potentially execute arbitrary SQL commands. This could lead to unauthorized access to sensitive data or compromise of the Snowflake environment.

Authenticated low-privilege user access required.
SQL injection via crafted input parameters.
Potential for data exfiltration and account compromise.

Live Threat

Current exploitation, exposure, and threat context

Authenticated users with low privileges could execute unauthorized SQL commands, potentially leading to the compromise of the source database, unauthorized access to data across different tenants, or the exposure of sensitive Snowflake account information. This risk is present when the Snowflake Snowpark Python SDK is used and specific APIs, such as `DataFrameReader.dbapi()`, `DataFrameWriter.write()`, or `DataFrame.to_csv()`, are invoked with specially crafted inputs.

Source database access and data.
SQL injection via specific SDK APIs.
Unauthorized data exfiltration or read.

Operational Fix

Recommended remediation, mitigation, and detection steps

SQL injection vulnerabilities in the Snowflake Snowpark Python SDK may allow authenticated low-privilege users to escalate privileges and potentially compromise the source database. The first practical step is to identify where the affected SDK is used, confirm its reachability and business criticality, locate the accountable owner, and then plan remediation based on risk.

Application and platform teams should own remediation.
Verify SDK usage and impact within your environment.
Plan mitigation based on exposure and criticality.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the Snowflake Snowpark Python SDK?

The Snowflake Snowpark Python SDK is a library that allows developers to write Python code to perform data processing, transformation, and analysis directly within the Snowflake data platform. It simplifies complex tasks by providing familiar Python data structures like DataFrames that execute logic inside the database engine, rather than pulling all data into a local machine.

What does CWE-89 mean for CVE-2026-15062?

CWE-89 is the classification for SQL Injection, a weakness where an application does not properly sanitize user-provided input before using it in a database query. In this CVE, the vulnerability allows an attacker to inject their own malicious SQL commands into specific SDK functions, tricking the system into executing unauthorized operations that go beyond the user's intended permissions.

How does an attacker trigger these SQL injection flaws?

An attacker needs to provide specially crafted inputs to specific SDK methods like DataFrameReader.dbapi(), DataFrameWriter write operations, or DataFrame.to_csv(). Simply having access to the library is not enough; the vulnerability is only triggered when these functions process malicious strings, such as embedding SQL payloads in column names or using escape sequences to bypass path sanitization.

Is this vulnerability likely to be reachable?

According to Halo Surface Signal, this is very unlikely to be exposed as a public-facing network service. The vulnerability exists within a library used in developer workflows or internal data pipelines. Because it requires a user to be already authenticated and interacting with the SDK in a local or integrated environment, it does not function as an open internet gateway.

What should I do first if I use this SDK?

Your first step is to inventory your projects to identify which services or applications depend on versions of the Snowflake Snowpark Python SDK prior to 1.53.0. Once identified, consult your development teams to confirm where these specific data-handling APIs are being used, then prioritize updating the library to the patched version as part of your standard maintenance cycle.

References

github.com/snowflakedb/snowpark-python/blob/main/CHANGELOG.md

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.