dbcve.org
CursorApplication · Anysphere

CVE-2025-64108

HIGH · 8.8 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 2.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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. In versions 1.7.44 and below, various NTFS path quirks allow a prompt injection attacker to circumvent sensitive file protections and overwrite files which Cursor requires human approval to overwrite. Modification of some of the protected files can lead to RCE. Must be chained with a prompt injection or malicious model attach. Only affects systems supporting NTFS. 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 versions 1.7.44 and below contain NTFS path handling quirks that allow prompt injection attackers to bypass sensitive file protection mechanisms and overwrite protected files without human approval. When critical files are modified, this can lead to remote code execution. The attack requires chaining with a prompt injection or malicious model attach and only affects NTFS-based systems.

MitigationUpgrade Cursor to version 2.0 or later, which contains the fix for this vulnerability. Organizations using NTFS filesystems should prioritize this upgrade given the high CVSS score and RCE potential.

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

CVSS:3.1/AV:N/AC:L/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. Determine installed Cursor version
    Open Cursor, click on the profile/settings icon in the bottom-left, then go to 'About' to see the version number. Alternatively, on Windows check Programs and Features or run 'cursor --version' from command line if available.
    Affected if Version is 1.7.44 or below (any version < 2.0)
  2. Identify the filesystem type
    Open Command Prompt and run 'fsutil fsinfo volumeinfo C:' (or the drive where Cursor projects are stored). Look for 'File System Name : NTFS' in the output.
    Affected if The filesystem is NTFS - the vulnerability only applies on NTFS-formatted drives
  3. Verify if sensitive file protection is in use
    Check Cursor's workspace settings for file protection or approval requirements. Look for settings related to 'human approval for file changes' or 'protected files' in the settings.json or preferences.
    Affected if File protection mechanisms are enabled and configured - these can be bypassed according to the CVE description
  4. Assess exposure to prompt injection or model attach
    Review Cursor's configuration files (settings.json, .cursor/mcp.json if present) for model attach features or external prompt integrations. Check if the AI model interactions allow external input that could be injection-prone.
    Affected if Prompt injection vectors exist or model attach feature is enabled - these are required for the attack chain

You are affected if: (1) Cursor version is below 2.0, (2) your projects run on an NTFS filesystem, AND (3) you have prompt injection exposure OR model attach enabled, with file protection mechanisms that could 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 version 2.0 or later, which contains the fix for this vulnerability. Organizations using NTFS filesystems should prioritize this upgrade given the high CVSS score and RCE potential.

Recommended fix High confidence

2.0 or later

  1. Open Cursor and navigate to Help > Check for Updates to check your current version
  2. If your version is below 2.0, download Cursor version 2.0 or later from the official cursor.sh website
  3. Install the new version by following the standard update process
  4. After installation, verify the version by going to Cursor > About Cursor and confirm the version number is 2.0 or higher
Caveat Review release notes for version 2.0 for any potential breaking changes in workflow or settings

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