UTC

Data exfiltration through agents

Sensitive data leaves through the agent: in a tool call, a message, a link or an image URL the client loads. It usually follows an injection.

How it works
  1. 1An agent that can read private data and also reach the outside world can be made to connect the two.
  2. 2The data can leave in plain sight, in a URL parameter, a rendered image, an email or a file the agent writes somewhere public.
  3. 3Because the action uses the agent's own permissions, access controls see an authorised request.
Real cases on the map
  1. CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
  2. Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
  3. CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
  4. Criticalgemini-mcp-tool vulnerable to OS command injection and @file exfiltration via prompt quoting (CVE-2026-0755)gemini-mcp-tool
  5. CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
  6. HighMCP Atlassian: Arbitrary File Read & Exfiltration (Confused Deputy) in JIRA update_issuemcp-atlassian

Published advisories whose own titles describe this technique.

What to watch for
  • Outbound requests to new domains after private data was read
  • Private data in URLs, image links or messages
  • Unusual volume in tool outputs leaving the system
How to defend
  • Separate reading private data from sending data out, or require approval to combine them.
  • Restrict outbound destinations and rendering of remote content.
  • Watch for data in URLs and links.