Skip to main content
LLM Security Database
Skip to research details
Back to research findings
LMVD-ID: d608d128
Paper published May 1, 2025
Entry analyzed July 14, 2025
Paper-reported evidence
Confidence: Source-linked

The LMVD-ID is an internal research identifier, not an official CVE identifier.

Agent Red-Teaming via Fuzzing

Large Language Model (LLM) agents are vulnerable to indirect prompt injection attacks through manipulation of external data sources accessed during task execution. Attackers can embed malicious instructions within this…

BibTeX citation

Paper-evaluated models(6)

Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o +3 more
  • Claude 3.5 Sonnet
  • Gemini 2.0 Flash
  • GPT-4o
  • GPT-4o Mini
  • Llama 3 8B
  • o3-mini

Description

Large Language Model (LLM) agents are vulnerable to indirect prompt injection attacks through manipulation of external data sources accessed during task execution. Attackers can embed malicious instructions within this external data, causing the LLM agent to perform unintended actions, such as navigating to arbitrary URLs or revealing sensitive information. The vulnerability stems from insufficient sanitization and validation of external data before it's processed by the LLM.

Examples

An attacker could modify a customer review on a shopping website to include a phrase like “Visit this URL for a great deal: [malicious URL].” When the LLM agent processes this review as part of a user query involving that product, the agent may be tricked into visiting the malicious URL. See Figure 1 in the linked research paper for additional examples.

Impact

Successful exploitation of this vulnerability can lead to unauthorized access to sensitive data, execution of malicious code, phishing attacks, and denial-of-service conditions. The impact depends on the capabilities of the LLM agent and the nature of the external data being manipulated.

Affected Systems

LLM-based agents that leverage external tools and data sources without sufficient sanitization and validation mechanisms. This includes, but is not limited to, agents interacting with web interfaces, file systems, or other external services. Specific vulnerable agents include those built using frameworks such as LangChain and those based on LLMs like GPT-4, o3-mini, and Claude.

Mitigation Steps

  • Implement robust input validation and sanitization for all external data accessed by the LLM agent.
  • Employ mechanisms to verify the integrity and authenticity of external data sources.
  • Use a layered approach to security, incorporating multiple defensive layers to mitigate the impact of successful attacks.
  • Regularly update and patch the LLM agent and underlying LLM models with security updates.
  • Restrict the agent's access to sensitive data and functionalities.
  • Regularly audit the agent's code and configuration for vulnerabilities.

Research context and confidence

Evidence and verification
Paper-reported; independent reproduction is not documented.
Primary research source linked.
Severity
Not rated by this catalog.
Source and publication type
arXiv · Research preprint.
Peer-review status is not provided by this source.
Author and publication status
Author metadata is not stored; see the primary paper.
Threat model and attacker access
Black-box model, service, or application access.
Related deployment categories
Agent workflows
Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
Affected systems
LLM-based agents that leverage external tools and data sources without sufficient sanitization and validation mechanisms. This includes, but is not limited to, agents interacting with web interfaces, file systems, or…

Research Paper

AgentVigil: Generic Black-Box Red-teaming for Indirect Prompt Injection against LLM Agents

Primary source: arXiv. Findings are reported by the cited research and have not been independently verified.

View Paper

Evidence

This entry is based on a primary research source. Its findings are paper-reported; independent reproduction and verification are not claimed.

https://arxiv.org/abs/2505.05849