CVE-2026-13751: Snowflake CLI Server-Side Request Forgery via Arbitrary URL Fetch in !source/!load
Improper handling of untrusted remote references in Snowflake CLI versions prior to 3.19 allowed server-side request forgery. The SQL statement reader's !source/!load directives could reference remote URLs that were retrieved at runtime without sufficient restriction on the request destination. By supplying crafted SQL content processed through a vulnerable command path, an attacker could cause the victim's environment to issue unintended outbound requests to internal or otherwise non-public network locations, and could cause remote SQL content to be retrieved and executed in the context of the victim user's session. Successful exploitation requires the victim to process attacker-controlled content through a vulnerable command path and is limited by the privileges available to that session and environment. The fix is available in Snowflake CLI version 3.19, which adds an option to disable remote URL retrieval.
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.19 - Configuration
In Snowflake CLI 3.19, disable remote URL retrieval to prevent !source/!load from fetching remote URLs at runtime.
Snowflake CLI remote URL retrieval option = disable
Event History
Frequently Asked Questions
What is the severity of CVE-2026-13751?
CVE-2026-13751 has a critical severity score of 9.6.
How do I fix CVE-2026-13751?
To fix CVE-2026-13751, upgrade to Snowflake CLI version 3.19 or later.
What type of vulnerability is CVE-2026-13751?
CVE-2026-13751 is classified as a Server-Side Request Forgery (SSRF) vulnerability.
What versions of Snowflake CLI are affected by CVE-2026-13751?
CVE-2026-13751 affects versions of Snowflake CLI prior to 3.19.
How does CVE-2026-13751 impact Snowflake users?
CVE-2026-13751 allows untrusted remote URLs to be fetched, potentially compromising the server's security.