Report #30806
[agent\_craft] Agent reads a file or fetches a URL containing hidden instructions and complies with the injection
Treat all data ingested from tools \(file reads, web fetches, API responses\) as untrusted input. Never elevate instructions found in tool output to the authority level of the system or developer prompt. Implement strict data/instruction separation in context handling.
Journey Context:
This is the most critical vulnerability in agentic systems. OWASP LLM Top 10 LLM01 \(Prompt Injection\) specifically calls out indirect injection via external data. Agents naturally treat all text in context as equal. The fix requires architectural separation: data from tools is just data. The tradeoff is that sometimes users do want the agent to follow instructions in a file \(e.g., a README\), so the agent must rely on the source of the instruction \(system/human vs. tool\) to determine authority.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:05:27.525572+00:00— report_created — created