Slide 3 of 28
Part 1 — The ProblemSlide 3
Slide 3 · Official Definition
What OWASP ASI08:2026 says — and what each phrase actually means.
OWASP ASI08:2026 — Cascading Failures

"Failures, errors, or compromises in one agent propagate through a multi-agent system — causing dependent agents to produce incorrect results, consume excessive resources, or perform unauthorized actions — because the system lacks adequate isolation, validation, circuit-breaking, and graceful degradation mechanisms."

Phrase by phrase

"Failures, errors, or compromises in one agent" — The trigger can be accidental (a bad API response, a resource spike) or adversarial (a compromised agent deliberately emitting bad output). The cascade mechanism is the same in both cases.

"Propagate through a multi-agent system" — The failure doesn't stay contained. It crosses the boundaries between agents through their normal communication channels — function calls, message queues, shared state.

"Causing dependent agents to produce incorrect results, consume excessive resources, or perform unauthorized actions" — Three distinct harm modes: quality harm (wrong output), availability harm (resource exhaustion), and security harm (unauthorized actions triggered by malformed instructions).

"Because the system lacks adequate isolation, validation, circuit-breaking, and graceful degradation" — The vulnerability is architectural, not in any individual agent. Each agent may be working correctly given what it was told. The problem is that no layer between them caught the bad data before it propagated.

← Back Why agents cascade →