dbcve.org
CursorApplication · Anysphere

CVE-2025-61591

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, when MCP uses OAuth authentication with an untrusted MCP server, an attacker can impersonate a malicious MCP server and return crafted, maliciously injected commands during the interaction process, leading to command injection and potential remote code execution. If chained with an untrusted MCP service via OAuth, this command injection vulnerability could allow arbitrary code execution on the host by the agent. This can then be used to directly compromise the system by executing malicious commands with full user privileges. This issue does not currently have a fixed release version, but there is a patch, 2025.09.17-25b418f.

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's MCP (Model Context Protocol) OAuth authentication flow in version 1.7 and below fails to properly validate server identity, allowing an attacker impersonating a malicious MCP server to inject arbitrary commands during the OAuth interaction. This command injection vulnerability enables an attacker to achieve remote code execution with the full privileges of the user running Cursor.

MitigationApply the vendor patch (version 2025.09.17-25b418f or later) to Cursor. Until patched, avoid connecting Cursor's MCP to untrusted servers and only use verified, trusted MCP services for OAuth authentication.

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. Identify installed Cursor version
    Open Cursor, go to Help > About, or check the application metadata. On macOS this may be in /Applications/Cursor.app/Contents/Info.plist. On Windows check the file properties of Cursor.exe.
    Affected if The version is 1.7 or lower (1.7, 1.6.x, 1.5.x, etc.)
  2. Verify MCP feature is in use
    Check if Model Context Protocol (MCP) is configured in Cursor. Look in Cursor settings for MCP server configurations, typically found under Settings > Extensions > MCP or similar extension/AI settings areas.
    Affected if MCP servers or extensions are configured and actively in use within Cursor
  3. Review MCP OAuth configurations
    Inspect Cursor's configuration files for MCP server entries. Check user-level config directories such as ~/.cursor/ or %APPDATA%/Cursor/ for files containing 'mcp' or 'MCP' references, especially those with OAuth or server URL settings.
    Affected if MCP server entries with OAuth authentication URLs are present in the configuration
  4. Check for untrusted MCP servers
    Review the list of configured MCP servers and their associated URLs. Identify any servers that are not from known, trusted sources or that use HTTP instead of HTTPS for OAuth endpoints.
    Affected if Any MCP server points to an unverified or non-https endpoint, indicating potential exposure to the vulnerability

A user is affected if they are running Cursor version 1.7 or below AND have an MCP server configured with OAuth authentication, particularly one pointing to an untrusted or improperly secured endpoint.

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

Apply the vendor patch (version 2025.09.17-25b418f or later) to Cursor. Until patched, avoid connecting Cursor's MCP to untrusted servers and only use verified, trusted MCP services for OAuth authentication.

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