CVE-2026-13752: Snowflake CLI SQL Injection Vulnerability

CVE-2026-13752 Overview

CVE-2026-13752 is a SQL injection vulnerability [CWE-89] in Snowflake CLI versions prior to 3.19. The flaw stems from improper neutralization of parameters passed to vulnerable command paths. An attacker who supplies crafted values can force Snowflake CLI to execute unintended SQL statements inside the user's active Snowflake session. Exploitation requires the crafted values to reach vulnerable parameters, which can occur through socially engineered input, malicious repository configuration, or compromised automation feeding external values into the CLI. The scope of impact is bounded by the privileges assigned to the active session. Snowflake has published a fix in Snowflake CLI version 3.19, and users must upgrade manually.

Critical Impact
Successful exploitation lets attackers execute arbitrary SQL under the authenticated user's Snowflake session, exposing confidentiality, integrity, and availability of data accessible to that session.

Affected Products

Snowflake CLI versions prior to 3.19
Automation pipelines and CI/CD workflows invoking Snowflake CLI with externally sourced parameters
Developer workstations executing Snowflake CLI against repositories with attacker-controlled configuration

Discovery Timeline

2026-06-29 - CVE-2026-13752 published to the National Vulnerability Database (NVD)
2026-06-30 - Last updated in NVD database

Technical Details for CVE-2026-13752

Vulnerability Analysis

Snowflake CLI is a command-line client for interacting with Snowflake data warehouses. The vulnerability arises because certain command paths incorporate user-supplied parameter values into SQL statements without proper neutralization. When crafted input reaches these parameters, the CLI concatenates or interpolates values into SQL that the Snowflake session then executes.

Because the injected SQL executes inside the caller's authenticated session, it inherits every role, warehouse, and object privilege granted to that session. An attacker can therefore read, modify, or destroy any object the user can access, including tables, stages, tasks, and stored procedures. In automation contexts running with service accounts, impact expands to the automation identity's privilege set.

Root Cause

The root cause is missing or insufficient input sanitization on parameter values before those values are composed into SQL text. The CLI does not consistently use parameterized queries or bind variables for the affected command paths, so metacharacters such as quotes, semicolons, and comment markers are passed through unchanged.

Attack Vector

Attack delivery is network-adjacent to the victim workflow. The attacker does not connect to Snowflake directly. Instead, the attacker plants crafted values where the CLI will read them, for example in a repository configuration file, a shared automation variable, a downloaded manifest, or a prompt shown to a user. When the victim runs the CLI, the crafted value flows into a vulnerable parameter and executes as SQL. Exploitation requires user interaction and low-privilege access to a source the CLI trusts. See the Snowflake Security Advisory for the authoritative vulnerability details.

Detection Methods for CVE-2026-13752

Indicators of Compromise

Snowflake QUERY_HISTORY entries containing unexpected SQL fragments such as stacked statements, comment markers (--, /*), or UNION clauses originating from CLI sessions.
Snowflake CLI invocations sourcing parameter values from repository files, environment variables, or web content that was recently modified.
Access to sensitive objects (credentials, tokens, sensitive tables) from CLI sessions that do not normally touch them.
Presence of Snowflake CLI binaries at versions below 3.19 on developer or CI hosts.

Detection Strategies

Ingest Snowflake ACCOUNT_USAGE.QUERY_HISTORY and alert on CLI-originated queries containing SQL metacharacters inside string parameters.
Baseline expected CLI command patterns per user and service account, and alert on divergence.
Inspect CI/CD logs for CLI arguments that include unexpected quoting or SQL syntax within values.

Monitoring Recommendations

Monitor process execution telemetry for snowflake or snow CLI processes and correlate command lines with the source of parameter values.
Track Snowflake CLI version inventory across endpoints and pipelines, and alert on versions below 3.19.
Enable Snowflake login and query auditing, and forward events to a SIEM for correlation with endpoint activity.

How to Mitigate CVE-2026-13752

Immediate Actions Required

Upgrade Snowflake CLI to version 3.19 or later on every workstation, build agent, and automation host.
Rotate Snowflake credentials and key pairs used by any session that ran a vulnerable CLI version against untrusted input.
Review QUERY_HISTORY for suspicious SQL executed by CLI sessions since the vulnerable versions were deployed.
Restrict service account privileges used by Snowflake CLI automation to the minimum required roles.

Patch Information

The fix is available in Snowflake CLI version 3.19. Upgrades are manual — the CLI does not self-update. Obtain the fixed release from the vendor distribution channel and follow the guidance in the Snowflake Security Advisory.

Workarounds

Avoid passing untrusted or externally sourced values to Snowflake CLI command parameters until the upgrade is complete.
Pin repository and pipeline configuration files under strict code review to prevent injection of malicious parameter values.
Run Snowflake CLI automation under least-privilege roles so that any injected SQL has minimal blast radius.

bash

# Verify installed Snowflake CLI version and upgrade to the fixed release
snow --version
pip install --upgrade "snowflake-cli>=3.19"
snow --version