dbcve.org
CursorApplication · Anysphere

CVE-2025-61590

HIGH · 7.5 CVSS v3.1 Published 2025-10-03
Fix available
A fix is available. Upgrade to 1.7 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cursor is a code editor built for programming with AI. Versions 1.6 and below are vulnerable to Remote Code Execution (RCE) attacks through Visual Studio Code Workspaces. Workspaces allow users to open more than a single folder and save specific settings (pretty similar to .vscode/settings.json) for the folders / project. An untitled workspace is automatically created by VS Code (untitled.code-workspace), which contains all the folders and workspace settings from the user's current session, opening up an entire new attack vector if the user has a .code-workspace file in path (either untitled created automatically or a saved one). If an attacker is able to hijack the chat context of the victim (such as via a compromised MCP server), they can use prompt injection to make the Cursor Agent write into this file and modify the workspace. This leads to a bypass of CVE-2025-54130 which can lead to RCE by writing to the settings section. This issue is fixed in version 1.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cursor versions 1.6 and below are vulnerable to RCE through Visual Studio Code Workspace files. Attackers with access to the chat context (e.g., via compromised MCP server) can use prompt injection to make the Cursor Agent write malicious configurations to .code-workspace files, modifying workspace settings to achieve RCE. This vulnerability bypasses CVE-2025-54130.

MitigationUpgrade Cursor to version 1.7 or later. Additionally, monitor for unauthorized modifications to .code-workspace files and audit MCP server integrations for compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CursorApplication
Affected:< 1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Cursor version
    Open Cursor, go to Help > About, or check the application bundle. Compare the version number to the affected range (versions below 1.7).
    Affected if Version is 1.6 or below
  2. Locate .code-workspace files in your project directories
    Search your workspace directories for .code-workspace files. These are JSON files with a .code-workspace extension that define multi-folder workspace configurations.
    Affected if You have .code-workspace files in your projects
  3. Inspect .code-workspace file contents for suspicious settings
    Open each .code-workspace file and examine the 'settings' section. Look for unexpected configurations in keys such as terminal.integrated.shell, terminal.integrated.shellArgs, remote.SSH.configFile, or any settings that specify executable paths or command-line arguments.
    Affected if Settings contain paths to executables or shell commands you did not configure
  4. Check for recent unauthorized modifications to .code-workspace files
    Review file modification timestamps on .code-workspace files using file system tools. Compare against known legitimate edit times or check version control history if available.
    Affected if Files were modified at unexpected times or without corresponding commit history

You are affected if your Cursor version is below 1.7 and you find .code-workspace files with settings you did not intentionally configure, particularly those involving shell or executable paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7 or later
Fixed in 1.7
Interim mitigation

Upgrade Cursor to version 1.7 or later. Additionally, monitor for unauthorized modifications to .code-workspace files and audit MCP server integrations for compromise.

Recommended fix High confidence

Cursor version 1.7

  1. Check current Cursor version by going to Help > About in the application menu
  2. Download Cursor version 1.7 or later from the official source (cursor.sh or cursor.com)
  3. Install the updated version by running the downloaded installer
  4. Restart Cursor to ensure the new version is fully loaded
  5. Verify the installed version is 1.7 or higher via Help > About

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cursor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61590 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data