CVE
CVE-2025-54136
- First Reported
- Jun 2, 2026
- Latest Reported
- Jun 2, 2026
CVE Enrichment
- CVSS
- 8.8 HIGH
- EPSS
- 28.26%
- EPSS Percentile
- 98.08%
- CISA KEV
- Not listed
Description
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.
Technical Details
- CVSS Version
- 3.1
- CNA / NVD Source
- security-advisories@github.com
- Published
- 02-Aug-2025 07:15
- Last Modified
- 17-Jun-2026 16:39
- EPSS Date
- 2026-10-12
- CWE
- CWE-78
CVSS Vector
CVSS:3.1 AV:N /
AC:L /
PR:L /
UI:N /
S:U /
C:H /
I:H /
A:H
Affected Products / Versions
- anysphere / cursor
Version / affected range: * · before (exclusive) 1.3
cpe:2.3:a:anysphere:cursor:*:*:*:*:*:*:*:*
References
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (1)
- malicious MCP server, September 2025), and MCPoison persistent code execution in Cursor IDE (CVE-2025-54136). MCP is no longer experimental infrastructure. It is the connective tissue of enterprise AI, and it Unauthenticated MCP Server Exposed AWS Credentials Through SSRF and File Inclusion
CVE (5)
Malware (2)
Threat Actors (1)
Vendors (3)
Products (7)
Tools (3)
Industries (4)
Countries (3)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.