Report #48816
[architecture] Downstream agents execute malicious instructions hidden in upstream agent outputs
Implement data/context tainting and strict role isolation. Treat any data gathered by an upstream agent as untrusted input, stripping it of directive authority using boundary tags \(e.g., \) and strictly instructing the downstream agent to only process data within those tags, never as commands.
Journey Context:
Multi-agent systems often pass the entire context window from one agent to the next. If Agent A browses the web and picks up a prompt injection, Agent B inherits this as a top-level directive. The tradeoff is context continuity vs. security. By marking inherited data as untrusted and using strict system prompts to bound agent behavior, you prevent privilege escalation across the chain, treating inter-agent data like user input.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:25:12.748151+00:00— report_created — created