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

171 entries

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

Natural Language Disguise Bypass

Published Analyzed Source: arXiv

LLM-based Code Interpreter Agents, including OpenInterpreter and OpenCodeInterpreter, are vulnerable to sandbox evasion and arbitrary code execution via Natural Language Disguise and Contextual Channel Injection. Attackers can bypass Abstract Syntax Tree (AST) static analysis and explicit input guardrails by transforming malicious code logic into descriptive natural language instructions (Code Descriptions), which successfully evade syntax-layer blocks. Additionally, attackers can bypass input…

CIBER: A Comprehensive Benchmark for Security Evaluation of Code Interpreter Agents
Evaluated models: GPT-3.5, GPT-4o, GPT-5

Role-Confusion Prompt Injection via Forged Reasoning

Published Analyzed Source: arXiv

The paper describes a reproducible prompt-injection failure in which low-privilege user or tool-output text that imitates a trusted role—especially a model’s reasoning style—is treated as authoritative. Its zero-shot, black-box “CoT Forgery” evaluation injects fabricated reasoning into user prompts and retrieved webpage/tool output. The authors report 60% average attack success on StrongREJECT and 56–70% success in an agent data-exfiltration evaluation, versus near-zero or substantially lower…

Prompt Injection as Role Confusion
Evaluated models: GPT-oss 20B, GPT-oss 120B, o4-mini+6 more
  • GPT-oss 20B
  • GPT-oss 120B
  • o4-mini
  • GPT-5 Nano
  • GPT-5 Mini
  • GPT-5
  • GLM-4.6
  • Kimi K2 Instruct
  • MiniMax M2

Agent Tool-Call Safety Gap

Published Analyzed Source: arXiv

LLM agents with tool-calling capabilities are vulnerable to a text-action modality divergence (termed the "GAP" vulnerability), where text-level safety alignment fails to transfer to tool-call execution. Attackers can craft adversarial prompts that cause the model to generate a text-based refusal (demonstrating text safety) while simultaneously executing the requested forbidden action through available external tools. Because text generation and tool-call selection operate through partially…

Mind the GAP: Text Safety Does Not Transfer to Tool-Call Safety in LLM Agents
Evaluated models: Claude Sonnet 4.5, GPT-5.2, Grok 4.1 Fast+3 more
  • Claude Sonnet 4.5
  • GPT-5.2
  • Grok 4.1 Fast
  • DeepSeek V3.2
  • Kimi K2.5
  • GLM-4.7

Long-Horizon Agent Attacks

Published Analyzed Source: arXiv

LLM agents equipped with tool-use, persistent memory, and environmental interaction capabilities are vulnerable to long-horizon attacks. Attackers can bypass single-turn safety guardrails by exploiting the temporal dimension of multi-turn interactions to incrementally steer agent behavior. The vulnerability manifests because the agent's safety mechanisms perform localized, single-step evaluations but fail to maintain semantic safety across extended interaction trajectories. This enables…

AgentLAB: Benchmarking LLM Agents against Long-Horizon Attacks
Evaluated models: GPT-4o, GPT-5.1, Gemini 3 Flash+1 more
  • GPT-4o
  • GPT-5.1
  • Gemini 3 Flash
  • Claude Sonnet 4.5

Structural Template Agent Hijack

Published Analyzed Source: arXiv

A vulnerability in LLM-based autonomous agents allows remote attackers to hijack agent execution via Structural Template Injection (STI). The flaw arises from the lack of strict architectural isolation between internal control tokens and untrusted external data during chat-template serialization. By embedding framework-specific special tokens (e.g., <|im_start|>, <|im_end|>, <tool_call>) and delimiter patterns into externally retrieved data sources (such as web pages, emails, or API…

Automating Agent Hijacking via Structural Template Injection
Evaluated models: GPT-4, GPT-4o, DeepSeek V3

Zombie Agent Persistence

Published Analyzed Source: arXiv

Self-evolving Large Language Model (LLM) agents that utilize long-term memory mechanisms (such as Vector Databases for Retrieval-Augmented Generation or Sliding Window buffers) are vulnerable to persistent indirect prompt injection. This vulnerability, termed "Zombie Agent," occurs when the agent's memory update function ($F_M$) processes attacker-controlled content retrieved from external sources (e.g., web pages, documents) and commits it to long-term storage without sufficient sanitization…

Zombie Agents: Persistent Control of Self-Evolving LLM Agents via Self-Reinforcing Injections
Evaluated models: Not reported

Automated Stealth Skill Injection

Published Analyzed Source: arXiv

A vulnerability exists in LLM-based coding agents that implement modular capability extensions (often referred to as "Agent Skills") where the agent dynamically loads and executes user-provided skill packages. The vulnerability allows for Skill-Based Prompt Injection, specifically leveraging a technique known as "SkillJect." This attack decouples the malicious intent from the operational payload to bypass semantic safety filters. An attacker constructs a skill package containing: 1. Inducement…

SkillJect: Effectively Automating Skill-Based Prompt Injection for Skill-Enabled Agents
Evaluated models: Claude Sonnet 4.6, GPT-5 Mini, GLM-4.7+7 more
  • Claude Sonnet 4.6
  • GPT-5 Mini
  • GLM-4.7
  • MiniMax M2.1
  • DeepSeek V4 Flash
  • GLM-5.1
  • MiniMax M2.7
  • MiMo V2.7
  • GPT-5.4
  • Claude Opus 4.6

LLM Guardrail Benchmark Lies

Published Analyzed Source: arXiv

Architectural limitations in Meta's Llama-Prompt-Guard-2-86M and Llama-Guard-3-8B cause them to fail at detecting indirect prompt injections and agentic tool-use attacks, with detection rates dropping as low as 7-37%. Llama-Guard-3-8B enforces strict user/assistant message alternation and lacks support for tool-use roles; attempting to process messages with role: "tool" or role: "ipython" causes the chat template to raise an error, preventing evaluation entirely. PromptGuard 2 operates…

When Benchmarks Lie: Evaluating Malicious Prompt Classifiers Under True Distribution Shift
Evaluated models: Llama 3 8B, Llama 3.1 8B

Personalized Agent Double Agent

Published Analyzed Source: arXiv

OpenClaw is vulnerable to Indirect Prompt Injection (IPI), Tool-Return Manipulation, and Persistent Memory Poisoning. The agent incorporates untrusted external content (e.g., fetched web pages) and external tool outputs directly into its observation stream without sufficient isolation. An attacker can embed malicious payloads into these external channels to hijack the agent's planning and execution trace. This allows the attacker to silently trigger high-privilege actions via OpenClaw's Skills…

From Assistant to Double Agent: Formalizing and Benchmarking Attacks on OpenClaw for Personalized Local AI Agent
Evaluated models: GPT-4o, Llama 3.1 70B, Qwen 2.5 7B

Untrusted Content Agent Overrule

Published Analyzed Source: arXiv

Tool-calling LLM agents are vulnerable to Indirect Prompt Injection (IPI) attacks that induce "Poisoned Chain-of-Thought (CoT)" persistence. When an attacker embeds fake system constraints or error traces into untrusted external content (e.g., tool outputs or retrieved documents), the agent may generate reasoning traces that accept these malicious constraints as ground truth. Even if the original injected input is later sanitized or removed, the residual poisoned reasoning traces remain in the…

CausalArmor: Efficient Indirect Prompt Injection Guardrails via Causal Attribution
Evaluated models: Gemini 2.5 Flash, Gemini 2.5 Pro, Claude Sonnet 4+1 more
  • Gemini 2.5 Flash
  • Gemini 2.5 Pro
  • Claude Sonnet 4
  • Gemini 3 Pro

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.