# CVE-2025-61591: Cursor CLI's Cursor Agent MCP OAuth2 Communication is Vulnerable to Remote Code Execution

> Attackers can execute arbitrary code on the host by impersonating a malicious MCP server during OAuth authentication in Cursor CLI.

- **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:** 3 Oct 2025
- **Updated:** 3 Oct 2025

## What is CVE-2025-61591?

CVE-2025-61591 is a high-severity command injection vulnerability in cursor, published on 3 Oct 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 1.7 and below, when MCP uses OAuth authentication with an untrusted MCP server, an attacker can impersonate a malicious MCP server and return crafted, maliciously injected commands during the interaction process, leading to command injection and potential remote code execution. If chained with an untrusted MCP service via OAuth, this command injection vulnerability could allow arbitrary code execution on the host by the agent. This can then be used to directly compromise the system by executing malicious commands with full user privileges. This issue does not currently have a fixed release version, but there is a patch, 2025.09.17-25b418f.

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

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

It affects 1 product.


Products: Anysphere Cursor.

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

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

## Is CVE-2025-61591 being exploited?

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

## Other vulnerabilities in cursor

- [CVE-2026-50548](https://insights.sbomify.com/CVE-2026-50548/): Cursor Desktop sandbox escape via agent-controlled working directory (critical 9.3)
- [CVE-2026-50549](https://insights.sbomify.com/CVE-2026-50549/): Cursor Desktop sandbox escape via symlink and failed path canonicalization (critical 9.3)
- [CVE-2025-64106](https://insights.sbomify.com/CVE-2025-64106/): Cursor: Speedbump Modal Bypass in MCP Server Deep-Link (high 8.8)
- [CVE-2025-64107](https://insights.sbomify.com/CVE-2025-64107/): Cursor is Vulnerable to Path Manipulation Using Backslashes on Windows (high 8.8)
- [CVE-2025-64108](https://insights.sbomify.com/CVE-2025-64108/): Cursor's Sensitive File Modification can Lead to NTFS Path Quirks (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61591 is a high-severity command injection vulnerability in cursor, published on 3 Oct 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-61591 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-61591/ (Markdown: https://insights.sbomify.com/CVE-2025-61591/index.md)
```

## Sources

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

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