CVE-2025-64108
BaseFortify
Publication date: 2025-11-04
Last updated on: 2025-11-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anysphere | cursor | to 2.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Cursor code editor versions 1.7.44 and below, where certain NTFS path quirks allow an attacker using prompt injection to bypass protections on sensitive files. This enables the attacker to overwrite files that normally require human approval to modify. Some of these files, if altered, can lead to remote code execution (RCE). The exploit requires chaining with a prompt injection or a malicious model attachment and only affects systems using NTFS. The issue is fixed in version 2.0.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to overwrite protected files within the Cursor code editor without user approval, potentially leading to remote code execution on the affected system. This could result in unauthorized control over the system, data compromise, or further exploitation.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Cursor to version 2.0 or later, as this version fixes the vulnerability. Additionally, avoid using vulnerable versions (1.7.44 and below) on systems supporting NTFS until the upgrade is applied.