Quick answers
- Is CVE-2026-13751 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13751 being exploited in the wild.
- How severe is CVE-2026-13751?
- Medium severity, with a CVSS score of 4.1, published 29 June 2026.
- Which products and versions are affected?
- Snowflake CLI 3.6.0 to 3.18.x (fixed in 3.19.0).
- Is there a fix for CVE-2026-13751?
- A patch was published on 2026-06-29: Fix released in Snowflake CLI version 3.19.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13751 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-13751?
- Check whether you run Snowflake CLI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Snowflake CLI versions 3.6.0 through 3.18.x contain a Server-Side Request Forgery (SSRF) vulnerability in the SQL statement reader. The root cause is improper validation of remote references within the '!source' and '!load' directives, which allow the retrieval of content from remote URLs at runtime. An attacker can exploit this by providing a crafted SQL file to a victim; when processed, the CLI may issue outbound requests to internal or non-public network locations. Furthermore, the CLI may retrieve and execute remote SQL content within the context of the victim's session. Exploitation requires user interaction (processing the malicious content) and is limited by the user's local and session privileges. Snowflake CLI version 3.19 addresses this by providing an option to disable remote URL retrieval.
Affected products
- Snowflake Snowflake CLI 3.6.0 to 3.18.x (fixed in 3.19.0)
Timeline
- 2026-06-29: advisory: Initial disclosure and NVD publication
- 2026-06-29: patched: Fix released in Snowflake CLI version 3.19.0