CVE-2025-54136: Cursor's Modification of MCP Server Definitions Bypasses Manual Re-approvals

Published Aug 1, 2025
·
Updated

Cursor is a code editor built for programming with AI. In versions 1.2.4 and below, attackers can achieve remote and persistent code execution by modifying an already trusted MCP configuration file inside a shared GitHub repository or editing the file locally on the target's machine. Once a collaborator accepts a harmless MCP, the attacker can silently swap it for a malicious command (e.g., calc.exe) without triggering any warning or re-prompt. If an attacker has write permissions on a user's active branches of a source repository that contains existing MCP servers the user has previously approved, or allows an attacker has arbitrary file-write locally, the attacker can achieve arbitrary code execution. This is fixed in version 1.3.

Affected Software

2 affected components
Cursor Cursor<=1.2.4
anysphere Cursor<1.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Cursor to a version that resolves this vulnerability.

    Fixed in 1.3
  2. Operational

    If you are affected on versions 1.2.4 and below, review MCP server configuration files that were previously approved in shared GitHub repositories and on the local target machine for any swapped malicious MCP definitions; revert them to the originally approved contents.

Event History

Aug 1, 2025
CVE Published
via MITRE·11:08 PM
Data Sourced
via MITRE·11:08 PM
DescriptionSeverityWeakness
Aug 2, 2025
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeaknessAffected Software
Jun 29, 2026
News Published
via Dark Reading·11:44 AM
News Published
via Dark Reading·06:46 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-54136?

CVE-2025-54136 is considered a high severity vulnerability due to its potential for remote and persistent code execution.

2

How do I fix CVE-2025-54136?

To fix CVE-2025-54136, update Cursor to version 1.2.5 or later to mitigate the vulnerability.

3

Who is affected by CVE-2025-54136?

CVE-2025-54136 affects all users of Cursor versions 1.2.4 and below.

4

What type of attack does CVE-2025-54136 enable?

CVE-2025-54136 enables attackers to achieve remote and persistent code execution through manipulation of trusted MCP configuration files.

5

Can CVE-2025-54136 be exploited locally?

Yes, CVE-2025-54136 can be exploited both remotely via a shared repository or locally on the target's machine.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203