Report #86985
[architecture] Agent B extracts sensitive data from tool outputs passed by Agent A via steganography or metadata leakage
Sanitize all tool outputs through allow-list filters before cross-agent handoff, stripping metadata, comments, and non-essential formatting including zero-width characters
Journey Context:
When Agent A uses a tool \(e.g., file read, database query\), the raw output may contain sensitive metadata \(file paths, user IDs, timestamps, comments\) or steganographic data \(invisible unicode, zero-width spaces\). Passing this raw output to Agent B creates a side-channel for data exfiltration or prompt injection attacks where B extracts hidden data or instructions. The defense is strict sanitization: parse tool outputs into structured data, extract only required fields via allow-lists, normalize text \(remove zero-width chars\), and strip all metadata before passing to downstream agents.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T04:35:47.735745+00:00— report_created — created