CVE-2026-15062: Snowflake Snowpark Python SDK · SQL Injection
Affects Snowflake Snowpark Python SDKSource CVE Database V5
Not known to be exploited · CVSS 9.6 Critical : upgrade to 1.53.0 as a priority.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.53.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade Snowflake Snowpark Python SDK to 1.53.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SnowflakeSnowpark Python SDK | Affected
| Fixed in
|
PyPIsnowpark-pythonpkg:pypi/snowpark-pythonOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor manages remediation for this cloud-hosted service. A patch is available in Snowpark Python SDK version 1.53.0 and later. Users should upgrade to version 1.53.0 or above to mitigate this vulnerability. Since this is a cloud service, Snowflake likely applies server-side mitigations; however, customers should verify their SDK versions and update accordingly. Patch status is confirmed as available.
Description
SQL injection vulnerabilities in the Snowflake Snowpark Python SDK (snowpark-python) versions prior to 1.53.0 could allow authenticated low-privilege users to execute SQL beyond their authorization scope. An attacker could exploit these vulnerabilities by embedding SQL payloads in source database column names to escalate privileges via the DataFrameReader.dbapi() API by supplying a specially crafted location parameter to DataFrameWriter write methods to redirect a COPY INTO to an arbitrary source query, or by including a backslash-single-quote sequence in an export path to defeat the normalize_path() sanitizer and inject SQL via DataFrame.to_csv(). Successful exploitation may result in source database compromise, unauthorized cross-tenant data exfiltration, or unauthorized read of Snowflake account data.