What is the CVSS score of EUVD-2026-40133?

EUVD-2026-40133 has a CVSS 3.1 base score of 6.3 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N. EPSS exploitation probability: 0.1%.

Is there a patch available for EUVD-2026-40133?

Yes, a patch is available for EUVD-2026-40133. Update the affected software to the latest version immediately.

Snowflake CLI EUVD-2026-40133

| CVE-2026-13748 MEDIUM

Path Traversal (CWE-22)

2026-06-29 SNOWFLAKE

GHSA-8394-2w3w-5r9h

Path Traversal Snowflake Cli

6.3

CVSS 3.1 · Vendor: SNOWFLAKE

Severity by source

Vendor (SNOWFLAKE) PRIMARY

6.3 MEDIUM

AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

vuln.today AI

6.3 MEDIUM

Local vector because victim must execute CLI on attacker content locally; PR:N as attacker needs no host privileges; UI:R for required victim action; S:C because data exits to Snowflake cloud; C:H for arbitrary file read with no integrity or availability impact.

3.1 AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (SNOWFLAKE).

CVSS VectorVendor: SNOWFLAKE

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Jun 29, 2026 - 18:01 EUVD

Analysis Generated

Jun 29, 2026 - 16:34 vuln.today

DescriptionCVE.org

Improper restriction of file path resolution in Snowflake CLI versions prior to 3.19 allowed arbitrary local file content to be read and transmitted to Snowflake services. An attacker could exploit this by supplying crafted repository or project content that referenced files outside the intended project boundary, causing Snowflake CLI to read local files and upload or embed their contents during deployment or SQL template processing. Successful exploitation required the victim to process attacker-controlled project content, and retrieval of exfiltrated data depended on access to the victim's Snowflake account artifacts such as query history or uploaded stage content. The fix is available in Snowflake CLI version 3.19, and users must manually upgrade.

AnalysisAI

Path traversal in Snowflake CLI versions prior to 3.19 enables arbitrary local file exfiltration to Snowflake cloud services when a victim processes attacker-controlled project or repository content. The CLI fails to restrict file path resolution during deployment or SQL template processing, allowing crafted project files to reference and transmit content from outside the intended project directory boundary to Snowflake-hosted artifacts. No public exploit has been identified and this CVE is not listed in the CISA KEV catalog; upgrade to version 3.19 is required as the vendor documents no supported workarounds.

Technical ContextAI

Snowflake CLI is the official command-line tool for interacting with Snowflake's cloud data warehouse platform, used by data engineers and developers for deployment workflows, SQL template processing, and stage management. The root cause is CWE-22 (Path Traversal / Improper Limitation of a Pathname to a Restricted Directory): the CLI does not canonicalize or sandbox file path references found in project configuration or SQL templates before resolving and reading them. As a result, an attacker-controlled project file can embed references such as relative traversal sequences (e.g., ../../.ssh/id_rsa) or absolute paths pointing to sensitive host files outside the project root. The CLI then reads and transmits those files to Snowflake stage storage or embeds them into SQL artifacts, completing the exfiltration. All versions captured by CPE cpe:2.3:a:snowflake:snowflake_cli:*:*:*:*:*:*:*:* prior to 3.19 are affected.

RemediationAI

Upgrade Snowflake CLI to version 3.19 or later, which is the vendor-confirmed fix per the advisory at https://community.snowflake.com/s/article/Snowflake-CLI-Vulnerability-Advisory; the vendor notes that upgrade must be performed manually as no automatic update mechanism is described. No vendor-documented workarounds exist. While upgrading, avoid executing Snowflake CLI deployment or SQL template commands against untrusted, community-sourced, or third-party project content. As a compensating control, restrict the filesystem context available during CLI execution: ensure working directories used for Snowflake CLI operations do not have sensitive directories (such as ~/.ssh, ~/.aws, or ~/.config) accessible via relative traversal. If potential exposure is suspected, review Snowflake account query history and uploaded stage contents for unexpected file artifacts, then rotate any credentials that may have been accessible on the affected host.