dbcve.org
CursorApplication · Anysphere

CVE-2025-64107

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.52 and below, manipulating internal settings may lead to RCE. Cursor detects path manipulation via forward slashes (./.cursor/./././././mcp.json etc.), and requires human approval to complete the operation. However, the same kind of manipulation using backslashes was not correctly detected, allowing an attacker who had already achieved prompt injection or some other level of control to overwrite sensitive editor files without approval on Windows machines. This issue is fixed in version 2.0.

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 editor versions 1.7.52 and below fail to detect path manipulation via backslashes on Windows, allowing an attacker with prior access (e.g., prompt injection) to overwrite sensitive editor files without the human approval that forward slash manipulation triggers. This enables RCE on Windows systems.

MitigationUpgrade Cursor to version 2.0 or later to receive the patch for this path traversal vulnerability.

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. Confirm Windows platform
    Verify the operating system is Windows (this vulnerability only affects Windows installations of Cursor)
    Affected if Running on Windows and the OS is vulnerable to backslash path manipulation in applications
  2. Check installed Cursor version
    Open Cursor, go to Help > About Cursor (or check the application metadata file in the installation directory) to find the exact version number
    Affected if The displayed version is below 2.0 (such as 1.7.52 or any version in the 1.x series)
  3. Verify version against affected range
    Compare your installed version number to the affected range: versions < 2.0
    Affected if Version is 1.7.52 or any version earlier than 2.0 on Windows
  4. Check for prompt injection exposure
    Review recent Cursor sessions, terminal history, or extension logs for any untrusted input that may have been processed (the attacker needs prior access such as prompt injection to exploit this flaw)
    Affected if Untrusted or external input has been processed by Cursor that could trigger file operations via path manipulation

You are affected if running Cursor version below 2.0 on Windows and the application has processed untrusted input that could trigger file write operations through backslash path traversal.

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 version 2.0 or later to receive the patch for this path traversal vulnerability.

Recommended fix High confidence

Cursor 2.0

  1. Check current Cursor version by opening the editor and navigating to Help > About Cursor
  2. Download Cursor version 2.0 or later from the official Cursor website or GitHub releases
  3. Install the new version by running the installer and following the on-screen prompts
  4. Restart Cursor after installation completes
  5. Verify the fix by confirming the version shows 2.0 or higher in Help > About Cursor

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

Fix this in Cursor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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