CVE-2026-13751
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 · uneditedImproper 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.
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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in Snowflake CLI where the SQL statement reader's !source and !load directives can fetch and execute SQL from attacker-controlled remote URLs without restrictions. An attacker can craft malicious SQL content that causes the victim's CLI to make outbound requests to internal or non-public network locations, then execute the retrieved SQL in the victim's session context.
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>= 1.1.0, < 3.19.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Snowflake CLI versionRun `snowflake --version` or `snow --version` to retrieve the CLI version numberAffected if The installed version is >= 1.1.0 and < 3.19.0
-
Inspect SQL files for !source or !load directivesSearch project directories, especially .sql files, for lines containing `!source` or `!load` followed by a URL (http:// or https://)Affected if SQL files contain `!source` or `!load` directives pointing to remote URLs that could be attacker-controlled
-
Review CLI command history for !source/!load usageCheck shell history files or any logged command outputs that may contain previous `snow` CLI invocations using !source or !load with URLsAffected if Command history shows recent use of !source/!load with remote URLs in the affected version range
-
Check for unexpected outbound network connectionsReview network logs, firewall logs, or proxy logs for connections originating from the CLI host to internal network ranges or unusual external IPs that coincide with CLI usage timesAffected if The CLI machine has made outbound HTTP/HTTPS requests to internal, loopback, or private network addresses (e.g., 127.0.0.1, 10.0.0.0/8, 192.168.0.0/16) that were not intentionally initiated by the user
A user is affected if they are running Snowflake CLI version 1.1.0 through 3.18.x and have used the !source or !load directives to load SQL from remote URLs, as this allows SSRF attacks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.19.0
Upgrade to Snowflake CLI version 3.19 or later and enable the option to disable remote URL retrieval. Avoid processing untrusted SQL content through !source/!load directives.
Snowflake CLI version 3.19.0 or later
- 1. Check current Snowflake CLI version by running 'snowflake --version' or 'snow -v'
- 2. If the version is less than 3.19.0, upgrade to version 3.19.0 or later using the appropriate package manager (e.g., pip install --upgrade snowflake-cli-labs, npm, or brew)
- 3. Verify successful upgrade by running 'snowflake --version' again and confirming the version is 3.19.0 or higher
- 4. (Optional) Review the new configuration option to disable remote URL retrieval if remote SQL loading is not needed in your environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13751 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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