dbcve.org
Snowflake CliApplication · Snowflake

CVE-2026-13744

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 of attacker-controlled content in Snowflake CLI versions prior to 3.19 allowed unintended SQL execution. By supplying crafted repository content, project configuration, manifest data, or specification input, an attacker could cause Snowflake CLI to execute unintended SQL in the context of the victim user's Snowflake session. Successful exploitation requires the victim to process attacker-controlled content through a vulnerable command path and is limited by the privileges assigned to that session. The fix is available in Snowflake CLI version 3.19. 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

Snowflake CLI versions before 3.19 fail to properly neutralize attacker-controlled input from repository content, project configuration, manifest data, or specification files. This allows injection of malicious SQL that executes within the victim's active Snowflake session, constrained only by the victim's assigned privileges.

MitigationManually upgrade Snowflake CLI to version 3.19 or later. Audit all workflows that process untrusted repository content or configuration files through the CLI.

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:>= 1.2.2, < 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 Snowflake CLI version
    Run `snowflake --version` or `snow --version` to display the installed CLI version
    Affected if The reported version is >= 1.2.2 and < 3.19.0, indicating the CLI is vulnerable to SQL injection via the affected command paths
  2. Identify project configuration files
    Locate snowflake.yml, snowflake.project, or similar project configuration files in your workspace directories using `find . -name 'snowflake*' -o -name '*.sfc' -o -name '*snow*'`
    Affected if Configuration files exist and were obtained from untrusted sources or contain suspicious SQL-like content in configuration fields
  3. Inspect manifest and specification input files
    Review any manifest.json, spec.yaml, or similar input files processed by the CLI for embedded SQL statements or unexpected command patterns
    Affected if Manifest or specification files contain SQL syntax embedded in fields that would be processed by vulnerable command paths
  4. Check repository content for injection vectors
    Examine any downloaded or cloned repository content that the CLI processes, looking for SQL statements embedded in file names, metadata, or configuration that the CLI might parse
    Affected if Repository content includes crafted SQL that could be executed in the Snowflake session context when processed by the CLI

A system is affected if Snowflake CLI version is 1.2.2 or higher but below 3.19.0 AND the CLI processes untrusted project configuration files, manifest data, repository content, or specification input that may contain malicious SQL statements.

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

Manually upgrade Snowflake CLI to version 3.19 or later. Audit all workflows that process untrusted repository content or configuration files through the CLI.

Recommended fix High confidence

Snowflake CLI 3.19.0

  1. Check current Snowflake CLI version using: snow --version or snowflake --version
  2. If version is >= 1.2.2 and < 3.19.0, upgrade to version 3.19.0
  3. Upgrade using your package manager (e.g., pip install --upgrade snowflake-cli-labs==3.19.0, or use brew/scoop depending on installation method)
  4. Verify the upgrade was successful by running snow --version and confirming it shows 3.19.0 or higher

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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