Cursor CurXecute: Prompt Injection to RCE via mcp.json
Cursor auto-updates and both bugs were fixed by mid-2025; the lasting takeaway is to treat any agent that can write its own tool config as a code-execution path.
Must act: Teams with Cursor installs frozen below 1.3.9 (CurXecute) or 1.3 (MCPoison), or that share repos containing .cursor MCP configs with untrusted contributors.
Can relax: Anyone on a current Cursor release with default approval prompts left on.
- Confirm every Cursor install is current (Help > About, or `cursor --version`); remove pinned or offline-installed old builds.
- Review committed `.cursor/mcp.json` files in shared repos and require code review for changes to them.
- Keep MCP approval prompts on and avoid broad auto-run settings for agent terminal commands.