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

65 entries

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

Self-Amplifying Memory Poisoning

Published Analyzed Source: arXiv

Large Language Model (LLM) agents utilizing long-term memory or Retrieval-Augmented Generation (RAG) are vulnerable to context-dependent memory injection attacks. Unlike traditional prompt injections that are overtly malicious, this vulnerability involves injecting records that appear benign and coherent in isolation—thereby bypassing standard perplexity filters and static content moderation (e.g., LlamaGuard). These records contain "sleeping" malicious logic that is only activated when…

A-memguard: A proactive defense framework for llm-based agent memory
Evaluated models: GPT-4o, Llama 3.1 8B

RL-driven Formalized Prompt Jailbreaking

Published Analyzed Source: arXiv

A vulnerability exists in aligned Large Language Models (LLMs) where a harmful instruction can be obfuscated through a multi-step formalization process, bypassing safety mechanisms. The attack, named Prompt Jailbreaking via Semantic and Structural Formalization (PASS), uses a Reinforcement Learning (RL) agent to dynamically construct an adversarial prompt. The agent learns to apply a sequence of actions—such as symbolic abstraction, logical encoding, mathematical representation, metaphorical…

Formalization Driven LLM Prompt Jailbreaking via Reinforcement Learning
Evaluated models: DeepSeek V3, Qwen 3 14B

Search Agents Vulnerable to Unreliable Results

Published Analyzed Source: arXiv

LLM-based search agents are vulnerable to manipulation via unreliable search results. An attacker can craft a website containing malicious content (e.g., misinformation, harmful instructions, or indirect prompt injections) that is indexed by search engines. When an agent retrieves and processes this page in response to a benign user query, it may uncritically accept the malicious content as factual and incorporate it into its final response. This allows the agent to be used as a vector for…

SafeSearch: Automated Red-Teaming for the Safety of LLM-Based Search Agents
Evaluated models: DeepSeek R1, Gemini 2.5 Flash, Gemini 2.5 Pro+11 more
  • DeepSeek R1
  • Gemini 2.5 Flash
  • Gemini 2.5 Pro
  • Gemma 3 27B IT
  • GPT-4.1
  • GPT-4.1 Mini
  • GPT-5
  • GPT-5 Mini
  • GPT-oss 120B
  • Kimi K2
  • o4-mini
  • Qwen 3 235B-A22B
  • Qwen 3 32B
  • Qwen 3 8B

Emergent Agentic Vulnerabilities

Published Analyzed Source: arXiv

GPT-OSS-20B exhibits "agentic-only" vulnerabilities where safety guardrails effective in standalone model inference fail when the model operates within an agentic execution loop. These vulnerabilities emerge when the model is deployed in a multi-step agentic architecture (e.g., utilizing LangGraph, tool usage, and memory retention). Attackers can bypass safety filters by employing context-aware iterative refinement attacks, which incorporate the full agentic state—including tool outputs…

Mind the Gap: Comparing Model-vs Agentic-Level Red Teaming with Action-Graph Observability on GPT-OSS-20B
Evaluated models: Not reported

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

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

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

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.