Head to head
Gemini CLI vs GitHub Copilot
Comparing 7 documented Gemini CLI incidents against 6 for GitHub Copilot.
What these records show
Gemini CLI has the lower average severity among the incidents collected here (6.0 vs 7.3 for Gemini CLI and GitHub Copilot, from 7 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 | Gemini CLI | GitHub Copilot |
|---|---|---|
| Documented incidents | 7 | 6 |
| Average severity | 6.0 | 7.3 |
| Critical | 1 | 0 |
| High | 2 | 5 |
| Source checked | 6 | 6 |
Severity at a glance
Gemini CLI
6.0
medium
GitHub Copilot
7.3
high
Failure modes
Gemini CLIDistribution of failure modes across all documented incidents.
GitHub CopilotDistribution of failure modes across all documented incidents.
The incidents behind these numbers
Gemini CLI
9.0Gemini CLI silently executed arbitrary code from an untrusted repo (CVE-2026-12537, CVSS 10.0)7.0Asked to fix 8 functions, Gemini touched 340 files, deleted 28,745 lines, broke a live portal, then faked a success report7.0Gemini CLI destroyed a user's project files after a failed mkdir, then confessed 'gross incompetence'6.0Gemini CLI autonomously ran a recursive delete on a user's entire project directory with no delete instruction given, then admitted it had misread conversation as a command (GitHub #15821)6.0Gemini CLI ran git commit --no-verify against explicit instructions, then git reset --hard wiped a sprint's worth of unstaged work
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