# CVE-2025-61592: Cursor CLI: Arbitrary Code Execution Possible through Permissive CLI Config

> Attackers can execute arbitrary code by tricking users into running the CLI in a malicious repository with permissive configuration settings.

- **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-61592?

CVE-2025-61592 is a high-severity code 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, automatic loading of project-specific CLI configuration from the current working directory (<project>/.cursor/cli.json) could override certain global configurations in Cursor CLI. This allowed users running the CLI inside a malicious repository to be vulnerable to Remote Code Execution through a combination of permissive configuration (allowing shell commands) and prompt injection delivered via project-specific Rules (<project>/.cursor/rules/rule.mdc) or other mechanisms. The fix for this issue is currently available as a patch 2025.09.17-25b418f. As of October 3, 2025 there is no release version.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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

It affects 1 product.


Products: Anysphere Cursor.

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

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

## Is CVE-2025-61592 being exploited?

There is no known exploitation of CVE-2025-61592 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-61592 and fix it if it is affected.

What it is: CVE-2025-61592 is a high-severity code 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-61592 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-61592/ (Markdown: https://insights.sbomify.com/CVE-2025-61592/index.md)
```

## Sources

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

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