# CVE-2025-64109: Cursor CLI Beta: Command Injection via Untrusted MCP Configuration

> Attackers can execute arbitrary code by tricking users into opening a malicious repository with Cursor CLI, which auto-runs untrusted MCP server commands.

- **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:** 4 Nov 2025
- **Updated:** 7 Nov 2025

## What is CVE-2025-64109?

CVE-2025-64109 is a high-severity command injection vulnerability in cursor, published on 4 Nov 2025. 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

Cursor is a code editor built for programming with AI. In versions and below, a vulnerability in the Cursor CLI Beta allowed an attacker to achieve remote code execution through the MCP (Model Context Protocol) server mechanism by uploading a malicious MCP configuration in .cursor/mcp.json file in a GitHub repository. Once a victim clones the project and opens it using Cursor CLI, the command to run the malicious MCP server is immediately executed without any warning, leading to potential code execution as soon as the command runs. This issue is fixed in version 2025.09.17-25b418f.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-64109?


## How do I fix CVE-2025-64109?

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

## Is CVE-2025-64109 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64109 and fix it if it is affected.

What it is: CVE-2025-64109 is a high-severity command injection vulnerability in cursor, published on 4 Nov 2025. 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-2025-64109 in the wild and no public exploit code.

Affected product: cursor. 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-2025-64109/ (Markdown: https://insights.sbomify.com/CVE-2025-64109/index.md)
```

## Sources

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

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