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

273 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

Deleted agent memory persists in live execution state

Published Analyzed Source: arXiv

Deleting a memory record can leave its information in an agent's summaries, pending plans and KV cache. The paper evaluates revocation across this derived execution state.

Forgetting Without Restarting: Execution-State Unlearning for Stateful LLM Agents
Evaluated models: Llama 3.1 8B Instruct, Qwen 2.5 7B Instruct, Mistral 7B Instruct v0.3

Context privilege escalation in AI agent harnesses

Published Analyzed Source: arXiv

Context assembly can promote repository, tool or skill content into higher-priority instructions or persistent state. The paper studies 12 pinned agent-harness versions.

What's in Your Agent's Context? Context Privilege Escalation Attacks against AI Agent Harness
Evaluated models: GPT-5.5, GPT-5.4-mini, Claude Sonnet 4.6+4 more
  • GPT-5.5
  • GPT-5.4-mini
  • Claude Sonnet 4.6
  • Claude Opus 4.6
  • Gemini 2.5 Flash
  • Gemini 2.5 Pro
  • DeepSeek V4 Flash

PII leakage in document-image redaction benchmarks

Published Analyzed Source: arXiv

Document-image PII detection can miss identifiers despite improving average localization scores. LeakageBench evaluates 500 pages with 11,954 annotations.

LeakageBench: Document-Level Leakage Risk for Redacting Personally Identifiable Information in Document Images
Evaluated models: GLiNER-base, GLiNER-multi-PII, NVIDIA GLiNER PII+5 more
  • GLiNER-base
  • GLiNER-multi-PII
  • NVIDIA GLiNER PII
  • GLiNER2
  • Qwen3-VL-32B
  • InternVL3 38B
  • GPT-5.4
  • GPT-5.5

Single-interaction poisoning of agent memory

Published Analyzed Source: arXiv

A stored interaction can later steer a memory-augmented agent's answer without direct memory-store access. The study evaluates persistent response manipulation in MemoryOS and MemGPT.

InjecMEM: Memory Injection Attack on LLM Agent Memory Systems
Evaluated models: Qwen 2.5 7B Instruct, Qwen 2.5 1.5B Instruct, Qwen 2.5 3B Instruct+3 more
  • Qwen 2.5 7B Instruct
  • Qwen 2.5 1.5B Instruct
  • Qwen 2.5 3B Instruct
  • Qwen 2.5 14B Instruct
  • Llama 3.1 8B Instruct
  • Mistral 7B Instruct v0.3

Unsafe shell commands can pass LLM agent dispatch guards

Published Analyzed Source: arXiv

Shell-command screening can miss harmful actions generated by coding agents. CARE combines static checks with optional model review at the command-dispatch boundary.

CARE: Pre-Execution Command Verification for Shell-Executing LLM Agents
Evaluated models: Qwen3-Coder-30B-A3B-Instruct, Granite Guardian 2B, Llama Guard 3 8B+1 more
  • Qwen3-Coder-30B-A3B-Instruct
  • Granite Guardian 2B
  • Llama Guard 3 8B
  • GPT-oss Safeguard 20B

Prompt injection across agent privilege boundaries

Published Analyzed Source: arXiv

Untrusted issue descriptions and tool responses can redirect privileged coding and tool agents. Twin Agent separates exploration from execution and restricts the information exchanged between them.

Twin Agent: Context Residual Compression for Privilege Separated Agents
Evaluated models: GPT-5.2, Gemini 2.5 Flash, Gemini 3.5 Flash

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.