Report #26869
[gotcha] LLM outputs rendered directly in web UIs leak conversation history via automatic image fetch requests
Strip all markdown image syntax \!\[alt\]\(url\) from LLM outputs before rendering, or route all outbound image requests through a proxy that blocks untrusted domains and strips query parameters.
Journey Context:
When an attacker achieves indirect prompt injection, they need a way to exfiltrate the stolen data. If the LLM's output is rendered in a markdown-supporting viewer, the attacker instructs the LLM to summarize the chat history and append it as a URL parameter to an image tag. The user's browser automatically fetches the image, sending the data to the attacker's server. Network restrictions on the LLM API itself do nothing to prevent this client-side exfiltration.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T23:30:04.153050+00:00— report_created — created