dbcve.org
CursorApplication · Anysphere

CVE-2025-61593

HIGH · 8.8 CVSS v3.1 Published 2025-10-03
Fix available
A fix is available. Upgrade to after 1.7 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 and below, a vulnerability in the way Cursor CLI Agent protects its sensitive files (i.e. */.cursor/cli.json) allows attackers to modify the content of the files through prompt injection, thus achieving remote code execution. A prompt injection can lead to full RCE through modifying sensitive files on case-insensitive filesystems. This issue is fixed in a commit, 25b418f, but has yet to be released as of October 3, 2025.

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 · moderate confidence

Cursor CLI Agent fails to properly protect sensitive configuration files (*/.cursor/cli.json) from modification through prompt injection. Attackers can inject malicious prompts to modify these sensitive files, which on case-insensitive filesystems can lead to arbitrary code execution with the privileges of the Cursor process.

MitigationSince the patch is not yet released, users should avoid running the Cursor CLI Agent with untrusted/provided prompts and monitor .cursor/cli.json for unauthorized modifications until version 1.8 or later is available.

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:<= 1.7

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. Check installed Cursor version
    Locate the Cursor application and query its version number (typically via About menu or application metadata)
    Affected if version is 1.7 or lower (the vulnerable versions)
  2. Verify CLI Agent feature usage
    Determine whether the Cursor CLI Agent has been invoked or configured - check for any CLI agent processes, logs, or configuration indicating recent agent usage
    Affected if CLI Agent feature has been used with external or untrusted prompts
  3. Inspect .cursor/cli.json for unauthorized changes
    Locate the .cursor/cli.json file in the user's home directory or project directory and examine its contents for any unexpected modifications or suspicious entries
    Affected if the file contains unexpected configurations or modifications you did not make
  4. Check filesystem type for case-insensitivity
    Identify if the filesystem is case-insensitive (default on Windows and macOS) - this is relevant because the vulnerability leverages case-insensitive file handling
    Affected if running on a case-insensitive filesystem (Windows APFS, macOS default)

You are affected if running Cursor version 1.7 or lower, have used the CLI Agent feature, and notice unexpected modifications to .cursor/cli.json especially on case-insensitive filesystems.

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 a release after 1.7
Interim mitigation

Since the patch is not yet released, users should avoid running the Cursor CLI Agent with untrusted/provided prompts and monitor .cursor/cli.json for unauthorized modifications until version 1.8 or later is available.

Recommended fix High confidence
  1. Monitor Cursor's official release channels for version 1.8 or later which should contain the security fix
  2. Do not use the Cursor CLI Agent with untrusted input until the patched version is available
  3. If using Cursor CLI Agent, avoid processing prompts from untrusted sources that could inject malicious instructions
  4. Review any automated pipelines using Cursor for potential prompt injection vectors

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

Fix this in Cursor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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