Head to head
Cursor vs GitHub Copilot
Comparing 4 documented Cursor incidents against 6 for GitHub Copilot.
What these records show
GitHub Copilot has the lower average severity among the incidents collected here (7.8 vs 7.3 for Cursor and GitHub Copilot, from 4 and 6 incidents). These records can't establish which agent is safer: counts reflect how widely each is used and how often people report failures, not a failure rate.
| Metric | Cursor | GitHub Copilot |
|---|---|---|
| Documented incidents | 4 | 6 |
| Average severity | 7.8 | 7.3 |
| Critical | 1 | 0 |
| High | 3 | 5 |
| Source checked | 4 | 6 |
Severity at a glance
Cursor
7.8
high
GitHub Copilot
7.3
high
Failure modes
CursorDistribution of failure modes across all documented incidents.
GitHub CopilotDistribution of failure modes across all documented incidents.
The incidents behind these numbers
Cursor
9.0Cursor's terminal sandbox trusted an agent-set working directory, letting zero-click prompt injection escape it and gain code execution (CVE-2026-50548)8.0Malicious cloned repository triggered code execution in Cursor on Windows7.0Cursor agent approved to delete one 18.5GB temp folder instead ran a mis-quoted rmdir that wiped a developer's source, Git repo, and six months of ERP backups7.0Cursor AI agent deleted PocketOS's entire production database and backups in 9 seconds
GitHub Copilot
8.0GitHub Copilot CLI ran arbitrary attacker commands via a nested bare git repository abusing core.fsmonitor (CVE-2026-45033)8.0GitHub Copilot suggested 2,702 valid secrets — 33% of extracted keys were real, live credentials8.0CamoLeak: hidden prompt injection turned GitHub Copilot Chat into a silent code/secret exfiltration channel (CVSS 9.6)8.0Rule Files Backdoor: hidden Unicode in config files made Copilot and Cursor emit malicious code7.0Copilot CLI's checkpoint restore ran git clean -fd and destroyed 1GB of evaluation data the agent never touched