Skip to main content
LLM Security Database
Skip to research search
Last analyzed Sep 9, 2026

Language Model Security Database

985 research findings · 1119 evaluated models

Filtered research findings

93 entries

Matches every word across titles, descriptions, sources, affected systems, and models.

Visual prompt injection crosses document trust boundaries

Published Analyzed Source: arXiv

Untrusted document images can redirect vision-language agents across instruction and tool-authorization boundaries. Repeat-After-Me evaluates six victim models on constructed document tasks.

Repeat-After-Me: Black-Box Adaptive Visual Prompt Injection
Evaluated models: claude-opus-4-7, GPT-5.5, Gemini 3.1 Pro+3 more
  • claude-opus-4-7
  • GPT-5.5
  • Gemini 3.1 Pro
  • Qwen3.6-27B
  • Qwen3-VL 32B Instruct
  • InternVL3.5 38B Instruct

Trajectory Poisoning in Self-Evolving Agent Skills

Published Analyzed Source: arXiv

Self-evolving agent-skill systems may promote recurring, attacker-controlled execution records into persistent reusable instructions. The paper evaluates whether poisoned but task-plausible trajectories survive aggregation and appear in generated skill artifacts, using inert canary behaviors and two structurally different skill-evolution pipelines.

When Experience Becomes Instruction: Trajectory Poisoning in Self-Evolving Agent Skill Systems
Evaluated models: GPT-5.4, MiniMax M2.5, DeepSeek V3.2+3 more
  • GPT-5.4
  • MiniMax M2.5
  • DeepSeek V3.2
  • DeepSeek V4-Pro
  • Qwen3.5-35B-A3B
  • Qwen3.5-122B-A10B

GhostWriter Persistent Memory Poisoning in Tool-Using Agents

Published Analyzed Source: arXiv

The paper describes GhostWriter, a reproducible two-phase attack against tool-using agents with persistent memory: untrusted email or calendar content is admitted into long-term memory, then later retrieved during a benign user task and treated as trusted context. In the authors’ controlled evaluation, this could steer subsequent agent actions despite the adversary lacking direct access to the agent, memory store, account, or later prompt. The paper reports an average 98% memory-injection rate…

When Agents Remember Too Much: Memory Poisoning Attacks on Large Language Model Agents
Evaluated models: GPT-5.4-mini, DeepSeek V4 Flash, Gemini 2.5 Flash+1 more
  • GPT-5.4-mini
  • DeepSeek V4 Flash
  • Gemini 2.5 Flash
  • Llama 3.1 8B

Automated indirect prompt injection against tool-calling agents

Published Analyzed Source: arXiv

The paper presents a concrete, reproducible security evaluation in which attacker-controlled instructions embedded in retrieved external content steer stateful, tool-calling LLM agents toward unauthorized actions. It adapts white-box GCG and black-box TAP to AgentDojo and evaluates single-task and task-universal attacks across 80 task pairs in four domains. The reported results show that semantic black-box optimization can discover functional prompt injections more effectively than…

Assessing Automated Prompt Injection Attacks in Agentic Environments
Evaluated models: Gemma3-4B Instruct, Qwen 3 4B Instruct, GPT-5+6 more
  • Gemma3-4B Instruct
  • Qwen 3 4B Instruct
  • GPT-5
  • GPT-5 Mini
  • Qwen 3 32B
  • Qwen3-235B-A22B (MoE)
  • Qwen3-235B-A22B-Thinking (MoE)
  • Claude Sonnet 4.5
  • Gemini 2.5 Flash

Persistent Memory Poisoning in LLM Agents

Published Analyzed Source: arXiv

The paper describes and evaluates a reproducible application-layer weakness in agents with persistent memory: untrusted external content can cross the memory-write boundary, be stored as trusted factual, experience, or procedural memory, and influence later sessions. It identifies four write channels—explicit writes, policy-driven writes, compaction, and experience-to-procedure synthesis—and six attack classes. For safe defensive testing, use MPBench’s two-phase structure in an isolated agent…

From Untrusted Input to Trusted Memory: A Systematic Study of Memory Poisoning Attacks in LLM Agents
Evaluated models: GPT-oss 120B

Sleeper Memory Poisoning in LLM Agents

Published Analyzed Source: arXiv

The paper presents a specific black-box indirect prompt-injection evaluation: attacker-controlled external content can cause a memory-enabled assistant or external memory manager to persist a fabricated user memory, which may later be retrieved in a separate session and steer responses or agent actions. The authors evaluate injection, retrieval, and conditional adversarial usage separately across synthetic document and future-session datasets. The released repository provides defensive…

Hidden in Memory: Sleeper Memory Poisoning in LLM Agents
Evaluated models: GPT-5.4, GPT-5.5, Claude Sonnet 4.6+3 more
  • GPT-5.4
  • GPT-5.5
  • Claude Sonnet 4.6
  • Gemini 3.1 Pro
  • Kimi-K2.6
  • DeepSeek V4-Pro

No-Prompt Reasoning Hijack

Published Analyzed Source: arXiv

An implicit reasoning hijacking vulnerability exists in Retrieval-Augmented Generation (RAG) and LLM-based agent frameworks. Attackers with write access to an agent's external memory or knowledge base can inject adversarially optimized malicious instances that trigger jailbreaks without requiring any modifications to the user's input prompt. The attack utilizes a shadow model to extract high-contribution subword tokens from anticipated benign user queries via log-probability changes and…

Stop Fixating on Prompts: Reasoning Hijacking and Constraint Tightening for Red-Teaming LLM Agents
Evaluated models: GPT-3.5 Turbo, GPT-4o, GPT-5+4 more
  • GPT-3.5 Turbo
  • GPT-4o
  • GPT-5
  • Llama 3.1 70B
  • Claude 3.5 Haiku
  • Gemini 3.0 Pro
  • ERNIE 3.5

Indirect Agent Privilege Exposure

Published Analyzed Source: arXiv

Autonomous LLM agents deployed in dynamic, multi-step tool-calling environments are highly vulnerable to Indirect Prompt Injections (IPI) embedded in external content. Surface-level defensive prompts and monitoring mechanisms (such as Prompt Warning, the Sandwich Method, Spotlighting, Keyword Filtering, and LLM-as-a-Judge) consistently fail to prevent exploitation and occasionally exacerbate the vulnerability by introducing adversarial distraction. While compromised agents exhibit…

Your Agent is More Brittle Than You Think: Uncovering Indirect Injection Vulnerabilities in Agentic LLMs
Evaluated models: Qwen 2.5 14B, Qwen 2.5 32B, Qwen 3 4B+6 more
  • Qwen 2.5 14B
  • Qwen 2.5 32B
  • Qwen 3 4B
  • Qwen 3 8B
  • Qwen 3 14B
  • Llama 3 8B
  • GLM 4 9B
  • Gemma 3 12B
  • Mistral 7B

Agent Implicit Doc Execution

Published Analyzed Source: arXiv

LLM-based coding agents are vulnerable to Document-Driven Implicit Payload Execution (DDIPE) via supply-chain poisoning of third-party agent skills. Attackers can embed malicious logic directly into legitimate-looking code examples and configuration templates within skill documentation files (e.g., SKILL.md). Because coding agents ingest this metadata into their context windows and treat the documentation as an authoritative reference, the underlying LLM silently reproduces and executes the…

Supply-Chain Poisoning Attacks Against LLM Coding Agent Skill Ecosystems
Evaluated models: Claude Sonnet 4.6, GLM-4.7, MiniMax M2.5+2 more
  • Claude Sonnet 4.6
  • GLM-4.7
  • MiniMax M2.5
  • GPT-5.4
  • Gemini 2.5 Pro

Observation Poisons Agent Memory

Published Analyzed Source: arXiv

Memory-augmented LLM web agents utilizing raw trajectory memory are vulnerable to Environment-injected Trajectory-based Agent Memory Poisoning (eTAMP). Attackers can embed malicious instructions within user-generated web content (e.g., product pages, forum posts). When the agent processes this content during a routine task, the instructions are passively ingested into its raw trajectory memory. During subsequent, entirely separate tasks on different websites, semantic retrieval mechanisms pull…

Poison Once, Exploit Forever: Environment-Injected Memory Poisoning Attacks on Web Agents
Evaluated models: GPT-5 Mini, GPT-5.2, GPT-oss 120B+3 more
  • GPT-5 Mini
  • GPT-5.2
  • GPT-oss 120B
  • Qwen 2.5 VL 72B
  • Qwen3-VL-32B
  • Qwen3.5-122B-A10B

Research methodology

Entries summarize publicly available primary-source security research. Model names reflect only systems explicitly evaluated by the cited paper, and measurements are research-reported unless independent verification is stated.

Discovery and publication are separate: new papers enter a candidate queue, then require human review and explicit approval before publication. Updates follow that review process, not a guaranteed daily publishing schedule. “Last analyzed” is the newest analysis date among published entries; it does not mean that all recent research has been covered.