CVE-2026-92903: Improper Input Validation in Snowflake CLI Versions Allow Unsanitized User-Controlled Values to be Interpolated into SQL Strings
Improper input validation in Snowflake CLI versions prior to 3.27.0 allowed unsanitized user-controlled values to be interpolated into SQL strings that are executed as multi-statement queries. An attacker who is able to supply a malicious project configuration file or craft command-line input can cause Snowflake CLI to execute attacker-controlled SQL statements in the context of the victim's Snowflake session and active role. Successful exploitation requires either write or pull-request access to a project repository whose CI/CD pipeline runs Snowflake CLI under an elevated service account role, or the ability to supply untrusted input to CLI-wrapping automation. Impact is limited by the privileges held by the configured Snowflake role at execution time. The fix is available in Snowflake CLI version 3.27.0, which also addresses several additional security findings. Users must manually upgrade.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Snowflake CLIto a version that resolves this vulnerability.Fixed in 3.27.0
Event History
Frequently Asked Questions
Which environments are realistically exposed?
Exposure requires a Snowflake CLI invocation that processes a malicious project configuration file or untrusted command-line input. A particularly relevant scenario is a CI/CD pipeline that runs the CLI using an elevated Snowflake service-account role and accepts changes from users with repository write or pull-request access.
What level of access does an attacker need?
The attacker needs either write or pull-request access to a project repository whose CI/CD pipeline runs Snowflake CLI under an elevated role, or the ability to provide untrusted input to automation that wraps the CLI. Exploitation also requires a victim session in which the CLI executes the supplied values.
What limits the impact, and what should be done if an immediate upgrade is not possible?
The attacker-controlled SQL runs with the privileges of the configured Snowflake role active at execution time, so limiting that role limits impact. Until upgrading, restrict who can modify project configuration or submit pull requests to relevant repositories, avoid passing untrusted input into CLI-wrapping automation, and avoid elevated roles where possible.
What is the available fix?
The fix is in Snowflake CLI 3.27.0, which also addresses additional security findings. Users must manually upgrade.