ACVE-2026-0201 · Hijack shown in a test · HIGH
WHAT HAPPENED
The agent calls a side-effecting tool with the arguments the injected text supplied, for example sending the user's security code or a transfer to the attacker.
THE SETUP — is yours like this?
WHAT TO CHANGE
Require approval for side-effecting tools, or separate or filter the tools.
- Reconfigure
agent.approvaltoask. A person decides before untrusted content can cause a side effect. Owner: operator - Reconfigure
harness.toolstoonly the tools the task needs, chosen before untrusted content is read. Recommended: AgentDojo's tool_filter cut GPT-4o's targeted ASR from 47.69% to 6.84%. Owner: harness-vendor - Reconfigure
model.toolResultstoinstructions inside tool results treated as data. Recommended: the benchmarks show the injection rate moves with the model. Owner: model-provider
HARM, REACH AND RECOVERY
SOURCES
ARTICLE
- https://arxiv.org/abs/2406.13352
- https://arxiv.org/abs/2403.02691
- https://arxiv.org/abs/2504.18575
- https://arxiv.org/abs/2410.02644
EVIDENCE
Technical details
An agent on any harness and any model, with side-effecting tools auto-approved or allowlisted, reads untrusted content that carries instructions and makes the tool call the content asked for.
Model as recorded: any
Reproducibility: partial (model availability not checked (no registry reference))
Claims
Confirmed means the statement matches the cited primary source. Nothing on this page has been reproduced.
Claims on this page have not been checked against primary sources.
Description
Threat
content-author · prompt-injection · harmful-action
What
Text returned by a web page, email, issue or MCP tool can carry instructions the model follows (indirect prompt injection). AgentDojo, InjecAgent, WASP and ASB measure how often it works; the rate moves with model, attack, defence and attempt count (see reference/model-injection-benchmarks.json). A successful injection runs any auto-approved tool with the user's authority.
Detection
The lockfile sees an untrusted-input tool, a side-effecting tool and the approval mode; it cannot see what content the agent reads or what task it was given.
Fix
Require approval for side-effecting calls, keep reading and acting in separate agents, or restrict the tool set per task: on the AgentDojo leaderboard tool_filter took GPT-4o from 47.69% to 6.84% targeted ASR.
Configuration
The rule ACVE's audit tool uses to recognise this configuration. The tool is not public yet.
and
some tools where
untrustedInput eq true
some tools where
sideEffect eq true
approval in ["never","allowlist"]Evidence
| Benchmark | Metric | Value | Attempts | Defence | Model | Source |
|---|---|---|---|---|---|---|
| AgentDojo leaderboard | targeted-asr | 0.4769 | — | none | gpt-4o-2024-05-13 | https://agentdojo.spylab.ai/results/ |
| AgentDojo leaderboard | targeted-asr | 0.0684 | — | tool_filter | gpt-4o-2024-05-13 | https://agentdojo.spylab.ai/results/ |