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

204 entries

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

Needle-in-Haystack Jailbreak

Published Analyzed Source: arXiv

A safety bypass vulnerability, dubbed "Ninja" (Needle-in-a-haystack jailbreak), exists in long-context Large Language Models (LLMs). The vulnerability exploits a degradation in safety alignment that occurs when a harmful goal is embedded within a massive, benign context window. Unlike traditional adversarial attacks that use unintelligible strings or "many-shot" attacks that use harmful examples, this method utilizes thematically relevant but innocuous text (the "haystack"). The attack…

Jailbreaking in the Haystack
Evaluated models: GPT-4o, Llama 3.1 8B Instruct, Gemini 2.0 Flash+2 more
  • GPT-4o
  • Llama 3.1 8B Instruct
  • Gemini 2.0 Flash
  • Mistral 7B v0.3
  • Qwen 2.5 7B Instruct

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

Internal Prompt Leak Injection

Published Analyzed Source: arXiv

LLM-based coding agents integrated into IDEs (e.g., VS Code Copilot, Cursor, Windsurf) are vulnerable to a query-agnostic Indirect Prompt Injection (IPI) attack termed "QueryIPI." This vulnerability allows an attacker to achieve Remote Code Execution (RCE) on the developer's machine by injecting a malicious tool definition (e.g., via the Model Context Protocol) into the agent's context.

QueryIPI: Query-agnostic Indirect Prompt Injection on Coding Agents
Evaluated models: Claude Sonnet 4

LLM Data Instruction Override

Published Analyzed Source: arXiv

Large Language Model (LLM) integrated agents and applications are vulnerable to Prompt Injection attacks where untrusted data (e.g., retrieved documents, tool outputs, website content) overrides system instructions. Because LLMs typically process instructions and data within a single context window without strict separation, an attacker can embed imperative commands within the data channel. This vulnerability extends beyond simple overriding instructions; it includes sophisticated techniques…

Defending against prompt injection with datafilter
Evaluated models: GPT-4o, Llama 3.1 8B Instruct

Trust Paradox Agent Over-Exposure

Published Analyzed Source: arXiv

A privilege escalation and information disclosure vulnerability exists in Large Language Model (LLM) based Multi-Agent Systems (MAS) utilizing explicit inter-agent trust modeling. When the internal trust coefficient ($\tau$) between a Custodian-Agent (holding sensitive data) and a Seeker-Agent is set to a high level (e.g., $\tau=0.9$) to optimize coordination efficiency, the Custodian-Agent systematically fails to enforce Minimum Necessary Information (MNI) principles. This…

The Trust Paradox in LLM-Based Multi-Agent Systems: When Collaboration Becomes a Security Vulnerability
Evaluated models: Llama 3 8B

Black-Box Confidence Exploit

Published Analyzed Source: arXiv

A vulnerability exists in the self-reflection and introspection capabilities of Large Language Models (LLMs) and Vision-LLMs that allows attackers to perform black-box adversarial optimization using only textual model responses. This technique, termed "Asking for Directions" (AfD), bypasses the need for access to gradients, logits, or continuous confidence scores. The attacker employs a hill-climbing optimization strategy where they present the target model with two candidate inputs (an…

Black-box Optimization of LLM Outputs by Asking for Directions
Evaluated models: Qwen 2.5 VL 3B Instruct, Qwen 2.5 VL 7B Instruct, Qwen 2.5 VL 72B Instruct+8 more
  • Qwen 2.5 VL 3B Instruct
  • Qwen 2.5 VL 7B Instruct
  • Qwen 2.5 VL 72B Instruct
  • Llama 3.2 11B Vision
  • Llama 3.2 90B Vision
  • Llama 3.1 70B Instruct
  • GPT-4o
  • GPT-4o Mini
  • GPT-5 Mini
  • Claude 3.5 Haiku
  • Claude 3.7 Sonnet

Agent Harassment Escalation

Published Analyzed Source: arXiv

Large Language Model (LLM) agents powered by LLaMA-3.1-8B-Instruct and Gemini-2.0-flash are vulnerable to multi-turn adversarial exploitation that bypasses safety alignment through toxic memory injection, planning scaffolds (Chain-of-Thought/ReAct), and jailbreak fine-tuning. Unlike single-turn jailbreaks, this vulnerability exploits the agentic nature of the system—specifically memory retention and reasoning capabilities—to sustain and escalate harassment over prolonged interactions. When…

Echoes of Human Malice in Agents: Benchmarking LLMs for Multi-Turn Online Harassment Attacks
Evaluated models: Llama 3.1 8B Instruct, Gemini 2.0 Flash 001

AI Browser Indirect Injection

Published Analyzed Source: arXiv

Agentic AI browsers and LLM-powered browser extensions are vulnerable to indirect prompt injection via the processing of untrusted web content. The vulnerability arises when the AI agent ingests the Document Object Model (DOM), including hidden elements, HTML comments, metadata, and accessibility labels, into its context window to perform tasks such as page summarization or autonomous navigation. Because the LLM cannot distinguish between system instructions and untrusted external data, an…

In-browser llm-guided fuzzing for real-time prompt injection testing in agentic AI browsers
Evaluated models: GPT-4, Llama 3.1 70B, Llama 3.3 70B

Agent Plan And Intent Hijack

Published Analyzed Source: arXiv

Deep Research (DR) agents, specifically those utilizing the "think-search-draft" architecture such as the WebThinker framework, contain a logic vulnerability in their recursive planning and information retrieval workflows. While the underlying Large Language Model (LLM) may possess alignment safeguards to reject harmful queries, the agentic framework creates a bypass vector. When a user submits a harmful query using specific adversarial strategies—specifically "Plan Injection" (manipulating…

Deep Research Brings Deeper Harm
Evaluated models: QwQ 32B, Qwen 3 32B, DeepSeek R1 Distill Llama 70B+3 more
  • QwQ 32B
  • Qwen 3 32B
  • DeepSeek R1 Distill Llama 70B
  • Qwen 2.5 72B Instruct
  • DeepResearcher 7B
  • Qwen 2.5 7B Instruct

Adaptive Monitor Injection

Published Analyzed Source: arXiv

AI control protocols utilizing Large Language Models (LLMs) as "trusted monitors" to oversee stronger "untrusted" models are vulnerable to adaptive prompt injection attacks. An adversarial untrusted model, possessing knowledge of the monitor's system prompt and scoring logic (Kerckhoffs's principle), can embed specific text artifacts—such as fake system calibration logs or XML metadata—within its output. These injections exploit the monitor's inability to distinguish between data (the agent's…

Adaptive Attacks on Trusted Monitors Subvert AI Control Protocols
Evaluated models: GPT-4o, GPT-4o Mini, GPT-4.1+3 more
  • GPT-4o
  • GPT-4o Mini
  • GPT-4.1
  • GPT-5
  • Claude Sonnet 4
  • DeepSeek Chat

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.