Incident database

AI agents break things.
Each failure gets an ID.

Like CVE, for AI coding agents. Every case where an agent caused real damage gets a STUPID-ID, a severity score against a published rubric, and a linked source you can check — 138 so far across 25 agents, one added most days. All of it queryable from inside your agent.

How this is built

Verified against source
125/138
Added in 14 days
14
Most recent
2026-10-29
Licence
CC BY 4.0

Every incident is scored against a published rubric and links to the source it was documented from. Where those sources come from: 65 github issue, 29 news report, 14 security research, 14 github pr, and 5 other kinds. Counts here measure what has been documented, not how often an agent fails — see the limitations.

Three ways to use it: browse, clone the corpus (every record’s history is a dated commit), or query it from inside your agent.

138
documented failures
6.0
avg severity /10
25
agents & models tracked
9
ranked agents

Most documented agents

Counts reflect how much a tool is used and reported — not how often it fails. Claude Code has the most documented incidents, at an average severity of 6.8. GPT-5.6-Sol's incidents average 8.3.

14 further agents are excluded — fewer than 3 documented incidents is not enough to rank on.

Latest reports

Severity distribution

Distribution of 138 incidents by severity score (0–10)
  • Critical 9–10
  • High 7–8
  • Medium 4–6
  • Low 0–3

Most common failure modes

Distribution of failure modes across all documented incidents.

Highest severity on record

STUPID-2026-0104
10.0critical

An AI vendor's automated evaluation sandbox was prompt-injected into handing over its production API keys for multiple AI providers, which the attacker then used against the vendor and ~30 other AI companies (Anthropic GTG-50020)

What is StupidLLM?

According to StupidLLM's incident database, 124 AI agent failures have been documented across 25 agents, plus 14 further multi-agent or unattributed reports — 138 in total — with an average severity of 6.0/10. Every incident is severity-scored using a CVSS-inspired rubric, linked to its source (most checked against it), and searchable by agent, failure mode, and root cause.

How are AI agent incidents scored?

Every incident is scored on a 0–10 scale. Scores of 9–10 are critical, 7–8.9 high, 4–6.9 medium, and below 4 low. The full rubric is on the methodology page.

Which AI coding agent has the most failures?

Claude Code has the most documented incidents (52), at an average severity of 6.8/10 — while GPT-5.6-Sol has the highest average severity at 8.3/10, with 3 documented incidents of its own. Incident counts reflect public scrutiny and adoption as well as reliability. Agents are only ranked once they reach 3 documented incidents. See the rankings above.

MCP server

Query this from inside your agent

Every incident here is callable over MCP — search by agent, failure mode or severity, and cite the source directly.

claude mcp add --transport http stupidllm https://www.stupidllm.com/api/mcp/

Read-only · no key · no signup

What you get back, and how to cite it

Incident alerts

Get told when an agent breaks something

We document AI agent failures daily, severity-scored against a published scale. Each Monday, if any scored 7 or above that week — deleted data, leaked secrets, broken production — you get one email with the sources. When nothing did, you get nothing.

Confirmation required. Unsubscribe in one click, from any email.