dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15062

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-08
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 Zero-click 6 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
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.

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

Multiple SQL injection vulnerabilities in Snowflake Snowpark Python SDK versions before 1.53.0 allow authenticated low-privilege users to bypass authorization through improper input sanitization in DataFrameReader.dbapi(), DataFrameWriter write methods (affecting COPY INTO), and DataFrame.to_csv() (via normalize_path() bypass). Attackers can inject SQL through malicious column names, crafted location parameters, or backslash-single-quote sequences in export paths.

MitigationUpgrade snowpark-python to version 1.53.0 or later to obtain patched sanitization in all affected API methods.

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

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. Check installed snowpark-python version
    Run 'pip show snowpark-python' or 'pip list | grep snowpark' to view the installed version
    Affected if Version is lower than 1.53.0 (e.g., 1.52.x, 1.51.x, etc.)
  2. Identify usage of DataFrameReader.dbapi()
    Search codebase for 'DataFrameReader' or '.dbapi(' calls, especially where column names may come from user input or external sources
    Affected if The method is used and version is below 1.53.0
  3. Identify usage of DataFrameWriter write methods with COPY INTO
    Search for 'write' or 'copy_into' method calls in snowpark code, check if location/table parameters accept user-controlled values
    Affected if COPY INTO operations are performed with user-supplied location or table parameters and version is below 1.53.0
  4. Identify usage of DataFrame.to_csv() with export paths
    Search for '.to_csv(' calls in snowpark code, examine if path arguments could contain backslash-single-quote sequences or be user-controlled
    Affected if to_csv() is used to export data and version is below 1.53.0

User is affected if snowpark-python version is below 1.53.0 AND any of the affected APIs (DataFrameReader.dbapi, DataFrameWriter COPY INTO, or to_csv) are used with untrusted input in column names, location parameters, or export paths.

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 snowpark-python to version 1.53.0 or later to obtain patched sanitization in all affected API methods.

Recommended fix Moderate confidence

snowpark-python version 1.53.0 or later

  1. Check current installed version of snowpark-python by running: pip show snowpark-python
  2. Upgrade to version 1.53.0 or later by running: pip install --upgrade snowpark-python
  3. Verify the upgrade was successful by running: pip show snowpark-python and confirming the version is 1.53.0 or higher
  4. If using in a requirements.txt or environment file, update the snowpark-python specification to: snowpark-python>=1.53.0
  5. Redeploy any applications or services that use the Snowpark Python SDK to ensure they run with the patched version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15062 — 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-15062 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