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

Research findings

985 entries

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

Content Concretization Jailbreak

Published Analyzed Source: arXiv

A vulnerability, termed "Content Concretization," exists in Large Language Models (LLMs) wherein safety filters can be bypassed by iteratively refining a malicious request. The attack uses a less-constrained, lower-tier LLM to generate a preliminary draft (e.g., pseudocode or a non-executable prototype) of a malicious tool from an abstract prompt. This "concretized" draft is then passed to a more capable, higher-tier LLM. The higher-tier LLM, when prompted to refine or complete the existing…

Jailbreaking Large Language Models Through Content Concretization
Evaluated models: Claude 3.5 Haiku, Claude 3.5 Sonnet, Claude 3.7 Sonnet+8 more
  • Claude 3.5 Haiku
  • Claude 3.5 Sonnet
  • Claude 3.7 Sonnet
  • Gemini 2.0 Flash
  • Gemini 2.5 Flash
  • Gemini 2.5 Pro
  • GPT-4
  • GPT-4.1
  • GPT-4o
  • GPT-4o Mini
  • o3

Multi-Agent Compositional Leak

Published Analyzed Source: arXiv

Multi-agent Large Language Model (LLM) systems are vulnerable to compositional privacy leakage, a flaw where sensitive information is exposed through the aggregation of individually benign responses from distinct agents. In distributed architectures where data is siloed (e.g., distinct agents handling HR, Finance, and IT logs), individual agents lack a global view of the user’s accumulated knowledge or the sensitive attributes derivable from cross-agent data combinations. An attacker can…

The Sum Leaks More Than Its Parts: Compositional Privacy Risks and Mitigations in Multi-Agent Collaboration
Evaluated models: Qwen 3 32B, Gemini 2.5 Pro, GPT-5

GUI Agent Dark Pattern Blindness

Published Analyzed Source: arXiv

Large Language Model (LLM)-powered GUI agents exhibit a vulnerability to deceptive interface designs (dark patterns) due to goal-driven optimization and procedural myopia. When executing natural language instructions on web interfaces, these agents consistently prioritize minimizing steps and achieving task completion over user safety or privacy. Agents frequently recognize manipulative elements—such as pre-selected consent checkboxes, hidden costs, or trick questions—in their internal…

Dark Patterns Meet GUI Agents: LLM Agent Susceptibility to Manipulative Interfaces and the Role of Human Oversight
Evaluated models: GPT-4o, Claude 3.7 Sonnet, DeepSeek V3+1 more
  • GPT-4o
  • Claude 3.7 Sonnet
  • DeepSeek V3
  • Gemini 2.0 Flash

Paper Submission Prompt Injection

Published Analyzed Source: arXiv

Large Language Models (LLMs) employed as automated assistants or autonomous agents in academic peer review systems are vulnerable to indirect prompt injection via maliciously crafted PDF submissions. Attackers can embed adversarial instructions within the manuscript that are invisible to human reviewers (using techniques such as white-on-white text or manipulating TrueType font character mapping tables) but are parsed and executed by the LLM.

When your reviewer is an llm: Biases, divergence, and prompt injection risks in peer review
Evaluated models: GPT-4o, GPT-5

Typos Undermine Watermarks

Published Analyzed Source: arXiv

Large Language Model (LLM) inference-time watermarking schemes are vulnerable to evasion via character-level perturbations that disrupt the model's tokenizer. Unlike token-level attacks (e.g., synonym replacement), character-level edits—such as homoglyph substitutions, zero-width character insertions, and typos—force the tokenizer to segment a single semantic unit into multiple sub-word tokens. This fragmentation alters the context window used by the watermarking hashing function (e.g., the…

Character-Level Perturbations Disrupt LLM Watermarks
Evaluated models: Llama 3 8B

Automated M2S Jailbreak Discovery

Published Analyzed Source: arXiv

Large Language Models (LLMs) are vulnerable to an automated Multi-turn to Single-turn (M2S) jailbreak strategy that utilizes evolutionary optimization to bypass safety guardrails. The "X-Teaming Evolutionary M2S" framework compresses adversarial multi-turn conversations into a single structured prompt. Instead of relying on static, hand-crafted jailbreaks, this vulnerability employs an LLM-guided evolutionary algorithm to dynamically generate and refine template structures (e.g., formatting…

X-Teaming Evolutionary M2S: Automated Discovery of Multi-turn to Single-turn Jailbreak Templates
Evaluated models: GPT-4.1, Claude Sonnet 4, Qwen 3 235B-A22B+2 more
  • GPT-4.1
  • Claude Sonnet 4
  • Qwen 3 235B-A22B
  • GPT-5
  • Gemini 2.5 Pro

Financial LLM Risk Concealment

Published Analyzed Source: arXiv

Large Language Models (LLMs) deployed in financial contexts are vulnerable to multi-turn adversarial attacks utilizing a "Risk-Concealment" strategy. The vulnerability arises from the failure of standard moderation layers and safety alignment to detect regulatory compliance risks (e.g., money laundering, insider trading) when obfuscated by professional domain jargon and seemingly legitimate business contexts. An attacker can exploit this by initializing a deceptive, policy-compliant seed…

Learning to Conceal Risk: Controllable Multi-turn Red Teaming for LLMs in the Financial Domain
Evaluated models: Llama 3.3 70B, Qwen 2.5 72B, Gemini 2.5 Flash+6 more
  • Llama 3.3 70B
  • Qwen 2.5 72B
  • Gemini 2.5 Flash
  • GPT-4o
  • Qwen 3 235B-A22B
  • GPT-4.1
  • Claude 3.7 Sonnet
  • o1
  • Claude Sonnet 4

Multimodal Prompt Injection

Published Analyzed Source: arXiv

Large Language Models (LLMs), including GPT-4o, LLaMA-3, and GPT-3.5-Turbo, are vulnerable to multimodal prompt injection attacks. These models fail to distinguish between system-level instructions and user-provided content within the context window. Attackers can exploit this by embedding malicious instructions in direct text, indirect sources (such as third-party webpages or PDFs), or visual inputs (images). Successful exploitation results in the model prioritizing the injected adversarial…

Multimodal Prompt Injection Attacks: Risks and Defenses for Modern LLMs
Evaluated models: GPT-3.5, GPT-4o, Llama 3 8B+1 more
  • GPT-3.5
  • GPT-4o
  • Llama 3 8B
  • Mistral Large 24B

EchoLeak Zero-Click Data Exfiltration

Published Analyzed Source: arXiv

A zero-click indirect prompt injection vulnerability, CVE-2025-32711, existed in Microsoft 365 Copilot. A remote, unauthenticated attacker could exfiltrate sensitive data from a victim's session by sending a crafted email. When Copilot later processed this email as part of a user's query, hidden instructions caused it to retrieve sensitive data from the user's context (e.g., other emails, documents) and embed it into a URL. The attack chain involved bypassing Microsoft's XPIA prompt injection…

EchoLeak: The First Real-World Zero-Click Prompt Injection Exploit in a Production LLM System
Evaluated models: Not reported

Camouflaged Jailbreak Prompts Benchmark

Published Analyzed Source: arXiv

Large Language Models from multiple vendors are vulnerable to a "Camouflaged Jailbreak" attack. Malicious instructions are embedded within seemingly benign, technically complex prompts, often framed as system design or engineering problems. The models fail to recognize the harmful intent implied by the context and technical specifications, bypassing safety filters that rely on detecting explicit keywords. This leads to the generation of detailed, technically plausible instructions for creating…

Behind the Mask: Benchmarking Camouflaged Jailbreaks in Large Language Models
Evaluated models: Gemma 3 4B IT, GPT-4, GPT-4o+2 more
  • Gemma 3 4B IT
  • GPT-4
  • GPT-4o
  • Llama 3.1 8B Instruct
  • Mistral 7B Instruct v0.3

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.