CVE-2025-64110
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 · uneditedCursor is a code editor built for programming with AI. In versions 1.7.23 and below, a logic bug allows a malicious agent to read sensitive files that should be protected via cursorignore. An attacker who has already achieved prompt injection, or a malicious model, could create a new cursorignore file which can invalidate the configuration of pre-existing ones. This could allow a malicious agent to read protected files. 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 confidenceA logic bug in Cursor versions 1.7.23 and below allows a malicious agent (via prompt injection or a malicious model) to create a new cursorignore file that overrides or invalidates pre-existing cursorignore configurations, thereby bypassing file protection mechanisms and allowing unauthorized reading of sensitive files that should be protected.
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< 2.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Cursor versionRun 'cursor --version' in terminal or check the application metadata (Help > About in the app) to determine the version numberAffected if Version is 1.7.23 or below, or any version below 2.0, meaning the logic bug in cursorignore file handling is present
-
Identify cursorignore files in workspaceSearch the project directory for files named 'cursorignore' using: 'find . -name "cursorignore" -o -name ".cursorignore"' or check in Cursor settings under protected filesAffected if One or more cursorignore files exist, as the vulnerability allows these to be overridden by a newly created malicious cursorignore file
-
Check cursorignore file content and precedenceExamine all cursorignore files found to see which files or patterns are marked as protected, noting their order and location in the filesystemAffected if Multiple cursorignore configurations exist (e.g., in different directories or with different scopes), as the logic bug allows a newly created cursorignore to override or invalidate pre-existing protections
-
Verify file protection settingsIn Cursor, go to Settings > Privacy & Security to review which directories or files are marked as protected from AI agent accessAffected if File protection rules are defined but could be bypassed if a malicious cursorignore file were created in any directory accessible to the AI agent
You are affected if running any Cursor version below 2.0 and using cursorignore file protection features, as a malicious agent could create a new cursorignore to bypass existing protections.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.0
Upgrade Cursor to version 2.0 or later, which contains the fix for this logic bug in cursorignore file handling.
Cursor 2.0
- Ensure you have a backup of your current Cursor configuration and workspace
- Open Cursor and check for updates via the application's update mechanism, or download Cursor version 2.0 from the official source
- Verify that the upgrade completed successfully by checking the Cursor version in the application settings or About section
- After upgrading, verify that existing cursorignore files are properly protecting sensitive files as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64110 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64110 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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