Head to head
Cline vs Cursor
Comparing 8 documented Cline incidents against 4 for Cursor.
Verdict
Cline has the lower average failure severity (5.7/10 vs 8.2/10), making it the statistically safer choice of the two — though both agents have documented critical incidents.
| Metric | Cline | Cursor |
|---|---|---|
| Documented incidents | 8 | 4 |
| Average severity | 5.7 | 8.2 |
| Critical | 1 | 3 |
| High | 1 | 0 |
| Verified | 8 | 4 |
Severity at a glance
Failure modes
The incidents behind these numbers
Cline
10.0Clinejection: an AI issue-triage workflow enabled arbitrary code execution on the CI runner7.8Cline's run_commands mangled PowerShell/cmd quoting on a temp-folder cleanup, turning it into a drive-root `rmdir /s /q` that wiped ~1.5TB of a user's photos, videos, and documents (GitHub #14864)5.8Cline's hub daemon silently reverted workspace files to stale state, repeatedly erasing a gitignored .env.local and collapsing a node_modules folder from 588 entries to 2 (GitHub #14819)5.8Cline's tool-call JSON repair silently executed truncated write_file and terminal arguments as valid4.8Cline sessions marked "failed" kept burning tokens for 20+ hours, and FREE-labeled models billed credits anyway
Cursor
10.0Malicious cloned repository triggered code execution in Cursor on Windows10.0Cursor AI agent deleted PocketOS's entire production database and backups in 9 seconds9.8Cursor's terminal sandbox trusted an agent-set working directory, letting zero-click prompt injection escape it and gain code execution (CVE-2026-50548)2.9Cursor's own support AI 'Sam' invented a one-device login policy, triggering subscription cancellations