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

609 entries

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

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

Adversarial RAG Context Poisoning

Published Analyzed Source: arXiv

Retrieval-Augmented Generation (RAG) systems in the health domain are vulnerable to corpus poisoning attacks where adversarial documents—specifically those generated via "Liar" (fabricated from scratch based on an incorrect stance) and "Few-Shot Adversarial Prompting" (FSAP)—are injected into the retrieval pool. When these adversarial documents are retrieved and presented as context, they successfully override the Large Language Model's (LLM) internal safety alignment and ground-truth…

Evaluating the Robustness of Retrieval-Augmented Generation to Adversarial Evidence in the Health Domain
Evaluated models: GPT-4.1, GPT-5, Claude 3.5 Haiku+3 more
  • GPT-4.1
  • GPT-5
  • Claude 3.5 Haiku
  • DeepSeek R1 Distill Qwen 32B
  • Phi-4
  • Llama 3 8B Instruct

Adversarial Report Code Insecurity

Published Analyzed Source: arXiv

Large Language Model (LLM)-based Automated Program Repair (APR) systems—such as SWE-agent, OpenHands, and AutoCodeRover—are vulnerable to adversarial manipulation via crafted bug reports. These systems accept unvetted natural language issue descriptions as trusted input to synthesize code patches. An attacker can exploit this trust by submitting semantically plausible but malicious bug reports designed to mislead the APR agent. By leveraging the semantic gap between natural language…

Adversarial Bug Reports as a Security Risk in Language Model-Based Automated Program Repair
Evaluated models: Prompt Guard, PromptGuard V2, Llama Guard 3+4 more
  • Prompt Guard
  • PromptGuard V2
  • Llama Guard 3
  • Llama Guard 4
  • Granite Guardian
  • GPT-4.1 Mini
  • o4-mini

Ethical Dilemma Jailbreak TRIAL

Published Analyzed Source: arXiv

A vulnerability exists in multiple Large Language Models (LLMs) where an attacker can bypass safety alignments by exploiting the model's ethical reasoning capabilities. The attack, named TRIAL (Trolley-problem Reasoning for Interactive Attack Logic), frames a harmful request within a multi-turn ethical dilemma modeled on the trolley problem. The harmful action is presented as the "lesser of two evils" necessary to prevent a catastrophic outcome, compelling the model to engage in utilitarian…

Between a Rock and a Hard Place: The Tension Between Ethical Reasoning and Safety Alignment in LLMs
Evaluated models: Claude 3.7 Sonnet, DeepSeek R1, DeepSeek V3+9 more
  • Claude 3.7 Sonnet
  • DeepSeek R1
  • DeepSeek V3
  • GLM 4 Plus
  • GPT-3.5 Turbo
  • GPT-4 Turbo
  • GPT-4o
  • Llama 2 13B
  • Llama 3 70B Instruct
  • Llama 3.1 8B
  • Qwen 2.5 7B
  • Vicuna 13B v1.5

Prompt Injection Alignment Bypass

Published Analyzed Source: arXiv

Large Language Models (LLMs) integrated with external retrieval mechanisms (e.g., Retrieval-Augmented Generation (RAG), web search, or email processing) are vulnerable to Indirect Prompt Injection. This vulnerability occurs when an LLM consumes input from untrusted external sources—such as websites, code repositories, or incoming emails—that contain embedded adversarial prompts. Unlike direct injection, where the user attacks the model, here the "poisoned" data is retrieved by the system…

Breaking to Build: A Threat Model of Prompt-Based Attacks for Securing LLMs
Evaluated models: Not reported

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.