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

41 entries

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

Voice Agent Behavioral Bypass

Published Analyzed Source: arXiv

Audio Large Language Models (ALLMs) integrated into voice agent systems for high-stakes domains (banking, IT support, logistics) are vulnerable to multimodal adversarial attacks via spoken interaction. Adversaries can exploit the model's inherent compliance and contextual awareness through multi-turn dialogue to bypass authentication safeguards, escalate privileges (e.g., unauthorized credit limit increases), exfiltrate sensitive Personally Identifiable Information (PII), and poison…

Aegis: Towards Governance, Integrity, and Security of AI Voice Agents
Evaluated models: GPT-4o, GPT-4o Mini, Gemini 1.5 Pro+4 more
  • GPT-4o
  • GPT-4o Mini
  • Gemini 1.5 Pro
  • Gemini 2.5 Flash
  • Gemini 2.5 Pro
  • Qwen2-Audio 7B
  • Qwen 2.5 Omni 7B

MCP Server-Side Injection

Published Analyzed Source: arXiv

The Model Context Protocol (MCP) specification v1.0 contains fundamental architectural vulnerabilities enabling server-side prompt injection and privilege escalation. The protocol relies on bidirectional sampling (sampling/createMessage) without cryptographic origin authentication or UI distinction, allowing connected servers to inject content that the LLM backend interprets as legitimate user input. Additionally, the protocol lacks isolation boundaries between concurrent server connections…

Breaking the Protocol: Security Analysis of the Model Context Protocol Specification and Prompt Injection Vulnerabilities in Tool-Integrated LLM Agents
Evaluated models: GPT-4o, Claude 3.5 Sonnet, Llama 3.1 70B

Agent Confused Deputy Escalation

Published Analyzed Source: arXiv

Multi-Agent Systems (MAS) orchestrated by Large Language Models (LLMs) are vulnerable to a Confused Deputy privilege escalation attack. This vulnerability arises when an untrusted or low-privilege agent exploits the inter-agent communication channel (e.g., broadcast or peer-to-peer messaging) to manipulate a high-privilege trusted agent into executing sensitive tools on its behalf. The root cause is the lack of mandatory access control policies governing agent-to-agent interactions; trusted…

Taming Various Privilege Escalation in LLM-Based Agent Systems: A Mandatory Access Control Framework
Evaluated models: o1

AI Agent Structural Blindspot

Published Analyzed Source: arXiv

A vulnerability in AI agent threat detection systems relying on standard conversational tokenization allows attackers to bypass security monitors and execute structural attacks, such as tool hijacking and data exfiltration. Because traditional NLP-based detectors focus on linguistic patterns (surface language) rather than execution flow, an attacker can orchestrate malicious multi-step tool sequences using entirely benign natural language. This structural blindness causes cross-attack…

Structural Representations for Cross-Attack Generalization in AI Agent Threat Detection
Evaluated models: Not reported

Cross-Environment Agent Jailbreak

Published Analyzed Source: arXiv

Large Language Model (LLM) agents operating in tool-augmented environments are susceptible to "Contextual Fragility" and multi-turn "long-chain" exploitation. Existing safety mechanisms predominantly function on a stateless, atomic paradigm, evaluating individual input-output pairs in isolation. This allows an adversary to orchestrate complex attack trajectories where malicious intent is distributed across multiple, individually benign steps (a "Domino Effect"). Consequently, an attacker can…

DREAM: Dynamic Red-teaming for Evaluating Agentic Multi-Environment Security
Evaluated models: o4-mini, Gemini 2.5 Flash, GPT-5+8 more
  • o4-mini
  • Gemini 2.5 Flash
  • GPT-5
  • Gemini 2.5 Pro
  • Grok 4
  • Claude Sonnet 4.5
  • Qwen 3 235B-A22B
  • Kimi K2 Preview
  • Llama 3.1 70B
  • Qwen 2.5 72B
  • DeepSeek V3.1

Pervasive Multi-turn Jailbreaks

Published Analyzed Source: arXiv

Multiple open-weight Large Language Models (LLMs)—specifically those prioritizing capability over safety alignment—exhibit a critical vulnerability to adaptive multi-turn prompt injection and jailbreak attacks. While these models effectively reject isolated, single-turn adversarial inputs (averaging ~13.11% Attack Success Rate), they fail to maintain safety guardrails and policy enforcement across extended conversational contexts. By leveraging iterative strategies such as "Crescendo" (gradual…

Death by a Thousand Prompts: Open Model Vulnerability Analysis
Evaluated models: GPT-oss 20B, Llama 3.3 70B Instruct, Mistral Large 2+5 more
  • GPT-oss 20B
  • Llama 3.3 70B Instruct
  • Mistral Large 2
  • DeepSeek V3.1
  • Qwen 3 32B
  • Gemma 3 1B
  • Phi-4
  • GLM 4.5 Air

Latent Space Discontinuity Exploitation

Published Analyzed Source: arXiv

A vulnerability exists in certain Large Language Models and diffusion models due to discontinuities in their latent space, which arise from data sparsity during training. An attacker can craft inputs containing lexically rare or semantically ambiguous constructs to guide the model's inference process toward these unstable, poorly-conditioned regions. This technique, termed "Alignment Degradation Induction," can degrade or bypass safety alignment mechanisms. Through iterative, multi-turn…

Exploiting Latent Space Discontinuities for Building Universal LLM Jailbreaks and Data Extraction Attacks
Evaluated models: Not reported

Mobile Agent Channel Subversion

Published Analyzed Source: arXiv

Mobile LLM-based agents (including Mobile-Agent-E, AppAgent, AutoDroid, and others) are vulnerable to indirect prompt injection attacks delivered via untrusted third-party mobile channels, such as in-app advertisements, system notifications, and embedded webviews. These agents utilize Multimodal Large Language Models (MLLMs) to perceive the device state via screenshots or accessibility trees. The vulnerability exists because the agents concatenate the user's prompt ($p$) with the environmental…

Measuring the Security of Mobile LLM Agents under Adversarial Prompts from Untrusted Third-Party Channels
Evaluated models: GPT-3.5 Turbo, GPT-4 Turbo, GPT-4o+1 more
  • GPT-3.5 Turbo
  • GPT-4 Turbo
  • GPT-4o
  • GPT-4.1 Mini

Distributed Backdoor in Multi-Agent Systems

Published Analyzed Source: arXiv

A distributed backdoor vulnerability, named "Collaborative Shadows", exists in LLM-based Multi-Agent Systems (MAS) that rely on external or modifiable tools. An attacker can poison multiple agent tools by embedding inert, encrypted "attack primitives" within them. These primitives are fragments of a larger malicious payload. A carefully crafted user instruction acts as both a trigger and a decryption key. The instruction steers the agents to collaborate in a specific sequence, causing them to…

Collaborative Shadows: Distributed Backdoor Attacks in LLM-Based Multi-Agent Systems
Evaluated models: Gemini 2.5 Pro, GLM 4.5, GPT-4.1+2 more
  • Gemini 2.5 Pro
  • GLM 4.5
  • GPT-4.1
  • Kimi K2 Instruct
  • Qwen 3 30B-A3B

Underestimated LLM Security Flaws

Published Analyzed Source: arXiv

Mamba-2 and hybrid Transformer-Mamba-2 distilled Large Language Model (LLM) architectures exhibit a distinct architectural susceptibility to Latent Injection and ANSI Escape sequence prompt injection attacks. Comparative analysis reveals that models incorporating Mamba state-space components (specifically distilled variants like Llamba-3B and base Mamba models) fail to maintain adversarial robustness levels comparable to pure Transformer baselines (such as Llama-3.2) when subjected to indirect…

Towards reliable and practical LLM security evaluations via Bayesian modelling
Evaluated models: Llama 3.2 3B, Falcon 7B

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.