Study reveals boundary laundering attacks in multi-Agent systems and proposes multi-CaMeL
Start here
A paper by researchers from Oxford University and other institutions in October 2026 (arXiv:2610.05640) found that even when every agent in a multi-agent system is deployed with CaMeL defenses, the system can still be compromised by indirect prompt injection. Attackers exploit "boundary laundering", causing data identified as untrusted to be executed by downstream agents as trusted instructions after being passed between agents; the paper demonstrates this process with a collaboration scenario involving three agents: orchestration, SQL, and notification. The authors accordingly propose the multi-CaMeL defense scheme.
Generated by AI from reports · Updated 22 days ago
Related research
Cited in the reports
Papers whose work the reports mention
- The reports mention AgentDojoAgentDojo: A Dynamic Environment to Evaluate Prompt Injection Attacks and Defenses for LLM AgentsIf every Agent is secure, why can the system still be breached? Cross-Agent trust laundering and dual-channel defenses
arXiv · 2024-06-19 · Deep reading
Storyline
- · 1 reports· Attention40multi-CaMeL Defends Against Multi-Agent Indirect Prompt Injection
- · 1 reports· Attention42
Study reveals boundary laundering attacks in multi-Agent systems and proposes multi-CaMeLThis event
Progress timeline
- WeChat · Mo'anjuSelectedIf every Agent is secure, why can the system still be breached? Cross-Agent trust laundering and dual-channel defenses
A paper from researchers at the University of Oxford and other institutions in October 2026 (arXiv:2610.05640) finds that even if every Agent in a multi-Agent system is deployed with CaMeL defenses, the system can still be breached by indirect prompt injection. Attackers exploit “Boundary Laundering,” causing data identified as untrusted to be executed downstream as trusted instructions after being passed across Agents; the paper demonstrates this process with a collaboration scenario involving three Agents: orchestration, SQL, and notification. The authors propose multi-CaMeL, which separates trusted instructions and data into two channels, message and variables, for transmission, and imposes instruction-channel integrity and cross-Agent provenance-preservation constraints. The authors also note that branch-guidance attacks do not violate their control-flow integrity definition, and that implicit data-dependency tracking still has limitations.