# CVE-2026-13749: Snowflake CLI Arbitrary Code Execution via Snowpark Annotation Processor Template Injection

> Attackers can execute arbitrary code locally by supplying crafted project content to the Snowflake CLI during bundling or deployment workflows.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-gxp8-hq7m-332h

## What is CVE-2026-13749?

CVE-2026-13749 is a high-severity code injection vulnerability in Snowflake CLI, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper neutralization in the Snowpark annotation processor callback template in Snowflake CLI versions prior to 3.19 allowed arbitrary code execution during application bundling or deployment. An attacker could exploit this by supplying crafted project content that is interpolated into generated Python code, causing Snowflake CLI to execute attacker-controlled code in the local context of the user running the CLI. Successful exploitation requires the victim to run the relevant bundling or deployment workflow against attacker-controlled project content, and any resulting code runs with the privileges of that local execution context. The fix is available in Snowflake CLI version 3.19, and users must manually upgrade.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-13749?

It affects 1 product.


Products: Snowflake Snowflake Cli.

## How do I fix CVE-2026-13749?

No fix has been published for CVE-2026-13749 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13749 being exploited?

There is no known exploitation of CVE-2026-13749 in the wild and no public exploit code.

## Other vulnerabilities in Snowflake CLI

- [CVE-2026-13744](https://insights.sbomify.com/CVE-2026-13744/): Snowflake CLI SQL Injection Through Improper Neutralization of User-Controlled Input (high 8.3)
- [CVE-2026-13748](https://insights.sbomify.com/CVE-2026-13748/): Snowflake CLI Arbitrary Local File Read and Exfiltration Through Improper File Path Restriction (medium 6.3)
- [CVE-2026-13752](https://insights.sbomify.com/CVE-2026-13752/): Improper neutralization of parameters in Snowflake CLI versions prior to 3.19 allowed unintended SQL execution. (medium 6.0)
- [CVE-2026-13750](https://insights.sbomify.com/CVE-2026-13750/): Snowflake CLI Sensitive Credential Exposure Through Debug Logging (medium 5.5)
- [CVE-2026-13751](https://insights.sbomify.com/CVE-2026-13751/): Snowflake CLI Server-Side Request Forgery via Arbitrary URL Fetch in !source/!load (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13749 and fix it if it is affected.

What it is: CVE-2026-13749 is a high-severity code injection vulnerability in Snowflake CLI, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-13749 in the wild and no public exploit code.

Affected product: Snowflake CLI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13749/ (Markdown: https://insights.sbomify.com/CVE-2026-13749/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13749
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13749
- OSV: https://osv.dev/vulnerability/CVE-2026-13749

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13749/
Summaries are generated and may contain mistakes; the official description above is the record.