Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

MCPoison

IdentifiersCVE-2025-54136CWE-494

A high-severity remote code execution vulnerability in Cursor, the AI-assisted code editor, affects versions 1.2.4 and earlier. The flaw is in Cursor’s handling of previously trusted Model Context Protocol (MCP) server configurations at the project level. After a user approves a benign MCP server, Cursor binds trust to the MCP/plugin identity rather than to the exact approved command content. An attacker who can modify an already trusted MCP configuration file can replace the original harmless command with a malicious one, and Cursor will execute the modified command without presenting a new warning or consent prompt. The vulnerable condition can be triggered by changing the MCP configuration inside a shared GitHub repository on a branch the victim uses, or by locally editing the configuration file on the target system. This enables silent execution of attacker-controlled commands such as calc.exe and, more generally, arbitrary OS command execution.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in remote and persistent arbitrary code execution in the victim’s development environment. Because the attack abuses an already approved MCP configuration, malicious command execution can occur without re-prompting the user, making the compromise stealthy and durable across repository updates or subsequent use of the workspace. Depending on the victim’s privileges and local environment, this can lead to full compromise of the developer workstation, access to source code and secrets available to the editor session, installation of persistence mechanisms, and follow-on actions such as credential theft or lateral movement.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid using Cursor with untrusted or collaboratively writable repositories that contain MCP server configurations. Restrict write access to active branches in repositories containing approved MCP definitions. Monitor and review changes to MCP configuration files as security-sensitive artifacts, and treat them like executable code. Prevent local arbitrary file-write conditions on developer systems, and consider isolating or sandboxing developer tooling that can spawn local commands from project configuration.

Remediation

Patch, then assume compromise.

Upgrade Cursor to version 1.3 or later, which fixes CVE-2025-54136. Replace vulnerable installations of Cursor 1.2.4 and earlier. Review repositories containing MCP server configuration files and validate that previously approved MCP definitions have not been modified. Revoke trust for existing MCP servers where possible and re-approve only known-good configurations after upgrade.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AnysphereCursorapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity19

Community discussion across Reddit, Mastodon, and other social sources.