dbcve.org
Snowflake CliApplication · Snowflake

CVE-2026-13749

HIGH · 8.8 CVSS v3.1 Published 2026-06-29
Fix available
A fix is available. Upgrade to 3.19.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 7 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
Improper neutralization in the Snowpark annotation processor callback template in Snowflake CLI versions prior to 3.19 allowed arbitrary code execution during application bundling or deployment. An attacker could exploit this by supplying crafted project content that is interpolated into generated Python code, causing Snowflake CLI to execute attacker-controlled code in the local context of the user running the CLI. Successful exploitation requires the victim to run the relevant bundling or deployment workflow against attacker-controlled project content, and any resulting code runs with the privileges of that local execution context. The fix is available in Snowflake CLI version 3.19, and users must manually upgrade.

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

A code injection vulnerability in Snowflake CLI versions before 3.19 allows attackers to execute arbitrary code via crafted project content that gets interpolated without proper sanitization into Python code templates during the Snowpark annotation processing callback. The malicious code executes in the local context of the user running the CLI bundling or deployment workflow.

MitigationUpgrade Snowflake CLI to version 3.19 or later and audit systems where users may run bundling/deployment workflows against untrusted project content.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Snowflake CliApplication
Affected:>= 2.4.0, < 3.19.0

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Snowflake CLI version
    Run `snowflake --version` or `snow --version` to display the CLI version number
    Affected if Version is 2.4.0 or higher but lower than 3.19.0
  2. Verify Snowpark module is available
    Run `snowflake snowpark` or check if Snowpark extension is installed via package manager
    Affected if Snowpark extension is installed and available in the CLI
  3. Identify project directories that may contain untrusted content
    Inspect directories containing Snowflake project.yml or similar project definition files, especially those received from external sources
    Affected if Project content from untrusted sources exists in the environment
  4. Check for recent bundling or deployment activity
    Review command history for `snowflake snowpark bundle`, `snowflake snowpark deploy`, or similar Snowpark build commands
    Affected if Bundling or deployment workflows have been executed recently
  5. Audit Python template processing
    Examine project directories for any Python template files (.py.j2, .py.tmpl) that get processed during Snowpark operations
    Affected if Project contains Python templates that get interpolated during build processes

A system is affected if Snowflake CLI version is between 2.4.0 and 3.18.x inclusive and users have run bundling/deployment workflows on project content containing potentially untrusted templates.

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
Upgrade available Upgrade to 3.19.0 or later
Fixed in 3.19.0
Interim mitigation

Upgrade Snowflake CLI to version 3.19 or later and audit systems where users may run bundling/deployment workflows against untrusted project content.

Recommended fix High confidence

3.19.0 or later

  1. Check the current installed version of Snowflake CLI using `snow --version` or `snowflake --version`
  2. Upgrade Snowflake CLI to version 3.19.0 or later
  3. Verify the upgrade was successful by checking the version again

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

Fix this in Snowflake Cli Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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