High

Cascading Failure Detection in Agent Pipelines

Multi-step AI agent pipelines often let each stage trust the previous one's output without a human checking in between. If a false signal, error, or manipulated result enters early, it can auto-approve, auto-rollback, or otherwise amplify itself through every downstream stage before anyone notices.

How the attack works

An attacker or a corrupted data source introduces a bad signal at an early pipeline stage — a false error, a manipulated output, or an injected instruction. Because stages are wired to auto-approve or auto-trigger actions based on the prior stage's output, no human checkpoint catches the problem. Each subsequent stage treats the bad signal as trustworthy and acts on it, often escalating the impact (e.g. triggering rollbacks, approvals, or further automated actions). The failure cascades and compounds rather than staying contained to one stage.

Netzilo detection

Netzilo reports this behaviour when it is observed.

Signature ID
b14e8f79-91c4-4670-9724-761295c9f754
Severity
High

Why it matters

A single corrupted or false input can cascade into wrong approvals, unwanted rollbacks, or a chain of automated actions across a whole pipeline, with no human intervention point to stop it — turning a small error into a large-scale operational or security incident.

What you can do

  • Insert human or independent verification checkpoints between pipeline stages instead of full auto-approval chains.
  • Require stages to validate inputs against their own criteria rather than blindly trusting the prior stage's output.
  • Add circuit breakers or rate limits so an error can't trigger unlimited automated actions downstream.
  • Log and review cross-stage signal propagation so cascades can be reconstructed and stopped early.

Known benign look-alikes

  • Legitimate pipeline monitoring reporting multi-stage errors for debugging
  • Chaos engineering or fault injection testing in controlled environments
  • Post-incident analysis discussing cascading failure root causes
  • Circuit breaker implementations that intentionally detect cascade patterns

References

Related threats