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

73 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

Persistent Agent Memory Poisoning and Incomplete Repair

Published Analyzed Source: arXiv

MemSecBench follows malicious agent-memory content from initial write through persistence, retrieval, action selection, execution, and attempted selective repair. Its controlled Write–Execute–Forget protocol evaluates 310 human-reviewed cases across two harnesses, four memory backends, three model backends, and seven evidence-gated lifecycle checkpoints.

MemSecBench: Tracking Agent Memory Poisoning from Persistence to Consequence and Repair
Evaluated models: GPT-5.5, DeepSeek V4-Pro, MiniMax-M3

Workspace Agent Runtime Safety Failures Across Risk Carriers

Published Analyzed Source: arXiv

AgentS4D measures unsafe actions and state changes across complete workspace-agent executions rather than treating task completion or isolated model responses as safety evidence. Its 328 sandboxed cases introduce risky content through user requests, documents, web resources, tools, third-party skills, and persistent memory, then compare the same cases across four agent harnesses and five model backends.

AgentS4D: Benchmarking Runtime Risks across the Execution Lifecycle of LLM-Based Workspace Agents
Evaluated models: GPT-5.5, Gemini 3.1 Pro, DeepSeek V4-Pro+2 more
  • GPT-5.5
  • Gemini 3.1 Pro
  • DeepSeek V4-Pro
  • MiniMax-M3
  • Qwen3.7-Plus

Incomplete MCP Tool-Call Attack Detection

Published Analyzed Source: arXiv

The MTGuard study evaluates unsafe Model Context Protocol tool calls originating from compromised server data, host-side execution changes, and malicious user-controlled resources. Its hybrid monitor combines pre-execution parameter inspection, behavioral observation, and post-execution result verification across browser-automation and financial-analysis agents.

Hybrid Analysis for Secure MCP Tool Use in LLM Agents
Evaluated models: GPT-5.6 Luna, DeepSeek V4 Flash, DeepSeek V4-Pro

Long-Context Enterprise Agent Policy Adherence Failures

Published Analyzed Source: arXiv

HANDBOOK.md measures whether an agent can apply detailed organizational rules while completing realistic, multi-step enterprise tasks. The vendor-authored benchmark includes 65 resettable MCP-backed workflows, policy documents of 20 to 124 pages, and 824 deterministic rubric checks covering required decisions, prohibited actions, and final environment state.

HANDBOOK.md: A Benchmark for Long-Context Agentic Instruction Following
Evaluated models: Claude Fable 5, GPT-5.6 Sol, Claude Opus 4.8+16 more
  • Claude Fable 5
  • GPT-5.6 Sol
  • Claude Opus 4.8
  • GPT-5.5
  • Grok 4.5
  • Muse Spark 1.1
  • GLM 5.2
  • Kimi K3
  • Gemini 3.5 Flash
  • Claude Sonnet 4.6
  • Gemini 3.1 Pro
  • DeepSeek V4-Pro
  • Qwen 3.7 Max
  • DeepSeek V4 Flash
  • Kimi-K2.6
  • Gemini 3.6 Flash
  • Gemini 3.5 Flash-Lite
  • Grok 4.3
  • Nemotron 3 Ultra

Black-Box System Prompt Leakage in Real-World LLM Applications

Published Analyzed Source: arXiv

The paper reports a reproducible black-box evaluation showing that adversarial user queries can cause deployed LLM applications to reveal hidden system prompts. In the authors’ measurement of 1,200 applications across six commercial platforms, 1,064 applications leaked prompt content (81.0%–93.5% per anonymized platform). This is a paper-reported result, not independently verified here. LeakBench and the official artifact repository provide defensive benchmark materials for controlled testing…

Understanding and Mitigating Prompt Leaking Attacks in Real-World LLM-Based Applications
Evaluated models: Llama 2 7B Chat, Llama 3.1 8B Instruct, Mistral 7B Instruct v0.3+5 more
  • Llama 2 7B Chat
  • Llama 3.1 8B Instruct
  • Mistral 7B Instruct v0.3
  • Qwen 3 4B Instruct 2507
  • Qwen 3 32B
  • Qwen 2.5 72B Instruct
  • Llama 3.3 70B Instruct
  • Qwen 3 30B-A3B Instruct-2507

Agent Skill Injection

Published Analyzed Source: arXiv

LLM-based personal agents are vulnerable to Indirect Prompt Injection (IPI) defense bypasses via declarative context reframing and implicit file provenance trust. Attackers can bypass agent safety filters by phrasing malicious instructions as declarative compliance alerts rather than imperative commands. Because agents are designed to report discrepancies as expected behavior, declarative framing bypasses intent-sensitive safety mechanisms. Additionally, attackers can exploit the agent's…

ClawSafety: Safe LLMs, Unsafe Agents
Evaluated models: Claude Sonnet 4.6, Gemini 2.5 Pro, DeepSeek V3+2 more
  • Claude Sonnet 4.6
  • Gemini 2.5 Pro
  • DeepSeek V3
  • Kimi K2.5
  • GPT-5.1

Stage-Sequential Agent Escalation

Published Analyzed Source: arXiv

Agentic Large Language Model (LLM) systems utilizing persistent memory, Retrieval-Augmented Generation (RAG) pipelines, and external tool connectors are vulnerable to Logic-layer Prompt Control Injection (LPCI). An attacker can inject obfuscated (e.g., encoded, structurally nested, or semantically reframed) payloads into external memory stores or RAG documents. These payloads bypass conventional inference-time plaintext content filters, persist across session boundaries, and remain dormant…

LAAF: Logic-layer Automated Attack Framework A Systematic Red-Teaming Methodology for LPCI Vulnerabilities in Agentic Large Language Model Systems
Evaluated models: GPT-4o Mini, Claude 3 Haiku, Llama 3.1 70B Instruct+2 more
  • GPT-4o Mini
  • Claude 3 Haiku
  • Llama 3.1 70B Instruct
  • Gemini 2.0 Flash
  • Mixtral 8x7B Instruct

Autonomous Agent Tool RCE

Published Analyzed Source: arXiv

The OpenClaw autonomous agent framework lacks execution sandboxing, running agents directly on the host machine with the disk and system privileges of the host user. This architecture allows attackers to achieve Remote Code Execution (RCE) and arbitrary data exfiltration via Indirect Prompt Injection. By embedding malicious instructions within external data sources (e.g., scraped web pages or uploaded documents), an attacker can hijack the agent's planning capabilities to sequentially chain…

Uncovering Security Threats and Architecting Defenses in Autonomous Agents: A Case Study of OpenClaw
Evaluated models: Not reported

Agent Document Instruction Injection

Published Analyzed Source: arXiv

High-privilege LLM agents with filesystem and network access are vulnerable to documentation-embedded instruction injection, an issue termed the "Trusted Executor Dilemma." When autonomously processing external workflow documents (e.g., README.md files or setup guides) during software installation workflows, agents implicitly trust and execute embedded text instructions without verifying their underlying intent. Attackers can embed syntactically valid, malicious directives (such as data…

You Told Me to Do It: Measuring Instructional Text-induced Private Data Leakage in LLM Agents
Evaluated models: GPT-4o, o3, o3-mini+5 more
  • GPT-4o
  • o3
  • o3-mini
  • GPT-oss 20B
  • Gemini 2.5 Pro
  • Gemini 2.5 Flash
  • Claude 3.5 Sonnet
  • Claude 3.7 Sonnet

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.