dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-64109

HIGH · 8.8 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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. 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.

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 CLI Beta automatically loads and executes MCP server configurations from .cursor/mcp.json files in cloned repositories without user warning or confirmation. When a victim clones a repository containing a malicious MCP configuration, the configured command runs immediately upon opening the project in Cursor, enabling remote code execution.

MitigationUpgrade Cursor to version 2025.09.17-25b418f or later, which addresses the automatic execution of untrusted MCP configurations.

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

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if Cursor is installed
    Run 'cursor --version' or 'cursor-beta --version' in terminal
    Affected if Cursor is not installed or command not found - not affected; if version prints, proceed to next checks
  2. Identify the Cursor version
    Run 'cursor --version' and note the full version string (e.g., 2025.09.17-25b418f)
    Affected if Version is below 2025.09.17-25b418f - potentially affected if Beta channel is active
  3. Confirm Beta channel usage
    Check if the installed Cursor is the Beta/Beta CLI version - look for 'cursor-beta' binary or Beta indicator in the version output
    Affected if Running Beta or Beta CLI version - the automatic execution vulnerability applies
  4. Search for .cursor/mcp.json files
    Run 'find /path/to/projects -name mcp.json -path "*/.cursor/*"' or manually inspect .cursor/ directories in cloned repositories
    Affected if Any .cursor/mcp.json file exists in project directories - those projects are vulnerable to RCE if the config contains malicious commands
  5. Inspect mcp.json for command execution
    Open any found .cursor/mcp.json and examine if the 'command' field contains arbitrary executable paths or scripts
    Affected if The mcp.json contains 'command' fields pointing to external executables or scripts - opening these projects in Cursor will auto-execute them

A user is affected if they run a pre-2025.09.17 Beta version of Cursor CLI and have cloned repositories containing .cursor/mcp.json files with configured commands, which will auto-execute upon project opening.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cursor to version 2025.09.17-25b418f or later, which addresses the automatic execution of untrusted MCP configurations.

Recommended fix High confidence

2025.09.17-25b418f (or latest stable release)

  1. 1. Check your current Cursor CLI version by opening Cursor and navigating to Help > About or running `cursor --version` in terminal
  2. 2. Download and install Cursor version 2025.09.17-25b418f or later from the official Cursor website (cursor.sh)
  3. 3. After upgrading, verify the new version is installed by checking Help > About
  4. 4. For existing projects with .cursor/mcp.json files, review the configuration before opening in Cursor to ensure it only contains trusted MCP server entries
  5. 5. Consider removing any untrusted .cursor/mcp.json files from repositories before cloning, or audit them after cloning but before opening in Cursor

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

Have this fixed 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 help mitigating

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-64109 — 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-64109 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