dbcve.org
Snowflake CliApplication · Snowflake

CVE-2026-13748

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-29
Fix available
A fix is available. Upgrade to 3.19.0 or later.
See remediation →
66/100
Remediation priority · Elevated
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 restriction of file path resolution in Snowflake CLI versions prior to 3.19 allowed arbitrary local file content to be read and transmitted to Snowflake services. An attacker could exploit this by supplying crafted repository or project content that referenced files outside the intended project boundary, causing Snowflake CLI to read local files and upload or embed their contents during deployment or SQL template processing. Successful exploitation required the victim to process attacker-controlled project content, and retrieval of exfiltrated data depended on access to the victim's Snowflake account artifacts such as query history or uploaded stage content. 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

Improper path traversal vulnerability in Snowflake CLI versions before 3.19 allows attackers to craft malicious project content that references files outside the intended project boundary, causing the CLI to read arbitrary local files and transmit their contents to Snowflake services during deployment or SQL template processing.

MitigationUpgrade Snowflake CLI to version 3.19 or later; avoid processing untrusted or attacker-controlled repository or project content until the upgrade is applied.

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:>= 0.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/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 Snowflake CLI version
    Run `snow --version` or `pip show snowflake-cli` to retrieve the installed version number
    Affected if The version is >= 0.2.2 and < 3.19.0
  2. Identify if CLI processes external or cloned project content
    Review whether you run `snow sql` or deployment commands on project directories from untrusted sources, shared repositories, or cloned templates
    Affected if The CLI processes project content that originates from untrusted or attacker-controlled sources
  3. Determine if SQL template or project file processing is used
    Check if your workflow includes running `snow sql` with template files, or using `snow app deploy` with project directories containing snowflake.yml or SQL files
    Affected if SQL template processing or project deployment features are actively used with external content

You are affected if Snowflake CLI version is between 0.2.2 and 3.19.0 AND you process untrusted or attacker-controlled project content via SQL templates or deployment commands

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; avoid processing untrusted or attacker-controlled repository or project content until the upgrade is applied.

Recommended fix High confidence

Snowflake CLI version 3.19.0

  1. Check the current installed version of Snowflake CLI using: snow --version or snowsql --version
  2. Upgrade Snowflake CLI to version 3.19.0 using your package manager (e.g., pip install --upgrade snowflake-cli-labs==3.19.0 or the appropriate method for your installation)
  3. Verify the upgrade was successful by running: snow --version
  4. Ensure any automated pipelines or scripts that run Snowflake CLI are updated to use version 3.19.0 or later

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

Fix this in Snowflake Cli Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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