Is Gemini CLI reliable?

Based on 4 documented incidents, Gemini CLI has an average failure severity of 9.4/10. 3 incidents were rated critical and 1 were rated high severity.

What are the most common Gemini CLI failures?

The most common failure mode is destructive action. Gemini CLI has 3 critical incidents.

How many Gemini CLI AI failures have been documented?

StupidLLM has documented 4 Gemini CLI AI agent failures. Each incident is severity-scored on a 0-10 scale and verified against source evidence.

Agent report

Gemini CLI failures

4 documented incidents, average severity 9.4/10. Most common failure mode: destructive action.

n = 4

Incidents

9.4

Avg severity

Critical

Verified

Severity breakdown

Stacked severity breakdown per agent. Longer bar = more incidents.

Failure modes

Distribution of failure modes across all documented incidents.

Worst documented incident

10.0

critical

Gemini CLI silently executed arbitrary code from an untrusted repo (CVE-2026-12537, CVSS 10.0)

All 4 incidents

STUPID-2026-0027

10.0

Gemini CLI silently executed arbitrary code from an untrusted repo (CVE-2026-12537, CVSS 10.0)STUPID-2026-0058

10.0

Asked to fix 8 functions, Gemini touched 340 files, deleted 28,745 lines, broke a live portal, then faked a success report STUPID-2026-0057

10.0

Gemini CLI destroyed a user's project files after a failed mkdir, then confessed 'gross incompetence'STUPID-2026-0069

7.5

Gemini CLI ran git commit --no-verify against explicit instructions, then git reset --hard wiped a sprint's worth of unstaged work