dbcve.org
CursorApplication · Anysphere

CVE-2025-61592

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, automatic loading of project-specific CLI configuration from the current working directory (<project>/.cursor/cli.json) could override certain global configurations in Cursor CLI. This allowed users running the CLI inside a malicious repository to be vulnerable to Remote Code Execution through a combination of permissive configuration (allowing shell commands) and prompt injection delivered via project-specific Rules (<project>/.cursor/rules/rule.mdc) or other mechanisms. The fix for this issue is currently available as a patch 2025.09.17-25b418f. As of October 3, 2025 there is no release version.

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 code editor versions 1.7 and below automatically loads project-specific CLI configuration from .cursor/cli.json in the current working directory, which can override global settings. Combined with project-specific Rules (.cursor/rules/rule.mdc) or other prompt injection vectors, this allows Remote Code Execution when users run the Cursor CLI inside malicious repositories.

MitigationAvoid running Cursor CLI in untrusted or malicious repositories until the official patch (2025.09.17-25b418f) is released as a stable version. Review and audit project-specific .cursor configuration files before running the CLI.

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 Cursor version
    Run `cursor --version` in terminal or open Cursor and navigate to Help > About to view the version number
    Affected if Version is 1.7 or lower (e.g., 1.6.x, 1.5.x, etc.)
  2. Locate .cursor directory in current project
    Run `ls -la .cursor/` in the terminal or check File Explorer visibility settings to reveal hidden folders in your project directory
    Affected if A .cursor/ directory exists in the working directory containing cli.json or rules/ subdirectory
  3. Inspect project-specific CLI configuration
    Open and review the contents of `.cursor/cli.json` if present - check for suspicious overrides to CLI settings, particularly command paths or execution parameters
    Affected if cli.json exists and contains configuration that overrides or redirects standard CLI behavior
  4. Check for project-specific prompt rules
    Examine `.cursor/rules/` directory for any .mdc or rule files - these can inject prompts that chain with the CLI config loading
    Affected if Rule files exist in .cursor/rules/ that could be used for prompt injection in combination with cli.json

You are affected if running Cursor version 1.7 or below AND opening or running CLI commands within a project directory that contains a .cursor/cli.json file, especially when .cursor/rules/ is also present.

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.

From vendor data
Upgrade available Upgrade to a release after 1.7
Interim mitigation

Avoid running Cursor CLI in untrusted or malicious repositories until the official patch (2025.09.17-25b418f) is released as a stable version. Review and audit project-specific .cursor configuration files before running the CLI.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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