dbcve.org
CursorApplication · Anysphere

CVE-2025-64106

HIGH · 8.8 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 2.0 or later.
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 1.7.28 and below, an input validation flaw in Cursor's MCP server installation enables specially crafted deep-links to bypass the standard security warnings and conceal executed commands from users if they choose to accept the server. If an attacker is able to convince a victim to navigate to a malicious deeplink, the victim will not see the correct speedbump modal, and if they choose to accept, will execute commands specified by the attackers deeplink.

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

A deep-link handling vulnerability in Cursor (versions 1.7.28 and below) allows specially crafted URLs to bypass the MCP server installation speedbump modal. Attackers can trick users into installing malicious MCP servers that execute attacker-controlled commands without proper security warnings.

MitigationUpgrade Cursor to a version above 1.7.28 which includes proper input validation for deep-links and ensures the security modal is always displayed before MCP server installation.

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:< 2.0

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. Identify Cursor version
    Open Cursor, go to Help > About or check the application metadata to confirm the exact installed version number
    Affected if The installed version is 1.7.28 or below, or any version less than 2.0
  2. Confirm MCP server functionality is accessible
    Verify that MCP (Model Context Protocol) server installation feature exists in the Cursor interface - typically found in Settings > Extensions or Settings > Integrations
    Affected if MCP server installation capability is present and accessible in the application
  3. Review recently installed MCP servers
    Check the Cursor settings or configuration files for any MCP server entries that may have been added recently, looking for unfamiliar or unexpected server configurations
    Affected if There are MCP servers installed that you did not intentionally configure or that appeared unexpectedly
  4. Inspect deep-link URL handling
    Examine whether Cursor processes deep-link URLs (such as cursor:// or similar URI schemes) - this can be verified by reviewing system browser handler registrations or Cursor's protocol handler configuration
    Affected if Cursor is registered as a handler for deep-link URLs and can be invoked via custom URL schemes

You are affected if running any Cursor version below 2.0 and the MCP server installation feature is accessible through deep-link URLs, as the security modal can be bypassed.

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 2.0 or later
Fixed in 2.0
Interim mitigation

Upgrade Cursor to a version above 1.7.28 which includes proper input validation for deep-links and ensures the security modal is always displayed before MCP server installation.

Recommended fix Moderate confidence

Cursor 2.0

  1. Open Cursor editor
  2. Navigate to the application menu (Cursor > Check for Updates on macOS or Help > Check for Updates on Windows/Linux)
  3. Allow Cursor to check for updates
  4. If version 2.0 or later is available, proceed with the update installation
  5. After updating, verify the version by going to Cursor > About Cursor (macOS) or Help > About (Windows/Linux) and confirm the version number is 2.0 or higher
Caveat Review Cursor 2.0 release notes for any new features or changes that may affect your workflow

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

Fix this in Cursor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64106 — 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-64106 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