Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

Is my AI tool safe?Coding agentsAnysphere

Is Cursor safe?

No tool is safe or unsafe on its own: it depends on what it can reach and how it is set up. The record for Cursor: 8 incidents in this center's library and 1 CVE in its advisory feed (1 critical), the newest published Aug 4, 2025. Below: what went wrong, what was fixed, and how to use it safely.

What to watch for

Most incidents share one shape: something the editor reads (a Slack message, a swapped MCP config, a support ticket, a rules file, a package's config) became instructions, and the agent ran them with the developer's permissions. On October 29, 2026 Cursor's own extension marketplace served a tampered Claude Code extension for about eleven hours that planted an SSH key, a reverse tunnel and startup items.

How to use it safely

Turn auto-run off for untrusted workspaces, review .cursor/ and rules files in code review, pin MCP servers to their tool lists, allow extensions only from approved publishers, and keep production credentials off developer machines.

What it can reach

  • Reads attacker-controlled content
  • Runs commands with your permissions
  • Holds API keys and tokens
  • Installs plugins, skills or tools from registries

What went wrong: incidents in the library

Known CVEs

  • CVE-2025-54135 Critical Cursor remote code execution via prompt-injected MCP config write
    Aug 4, 2025 · fixed in 1.3.9

How many people use it

A high CVE count can mean heavy scrutiny as much as weak engineering, so read the incidents and advisories, not only the number. The counts are what this center has recorded, not every flaw ever found; usage figures are the vendors' and registries' own published numbers.

Sources

Compare it with the others on the Technology watch list