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

35 entries

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

Agent Pipeline Simple Hacks

Published Analyzed Source: arXiv

Commercial LLM-powered agents utilizing autonomous web access, memory modules, and retrieval-augmented generation (RAG) are vulnerable to indirect prompt injection and environmental manipulation. Attackers can embed malicious instructions into external data sources trusted by the agent (such as Reddit posts, public databases, or ArXiv papers). When the agent autonomously retrieves and processes this content during task execution, it executes the embedded malicious commands. This vulnerability…

Commercial llm agents are already vulnerable to simple yet dangerous attacks
Evaluated models: Not reported

Unlearning Robustness Gap

Published Analyzed Source: arXiv

Post-hoc Large Language Model (LLM) unlearning and guardrailing mechanisms (specifically In-Context Unlearning [ICUL] and standard prompt-based Guardrailing) are vulnerable to information leakage attacks via "Target Masking" and indirect referencing. These systems rely on superficial semantic matching to suppress "forget sets" (specific entities or concepts). Attackers can bypass these restrictions by querying associated properties, relationships, or pseudonyms rather than the explicit target…

Alu: Agentic llm unlearning
Evaluated models: GPT-4o, Llama 2 7B, Llama 3.2 3B+2 more
  • GPT-4o
  • Llama 2 7B
  • Llama 3.2 3B
  • Qwen 2.5 14B
  • Phi-3

RL-Based LLM Privacy Leak

Published Analyzed Source: arXiv

Large Language Models (LLMs) are vulnerable to a novel agentic-based red-teaming attack, PrivAgent, which uses reinforcement learning to generate adversarial prompts. These prompts can extract sensitive information, including system prompts and portions of training data, from target LLMs even with existing guardrail defenses. The attack leverages a custom reward function based on a normalized sliding-window word edit similarity metric to guide the learning process, enabling it to overcome the…

PrivAgent: Agentic-based Red-teaming for LLM Privacy Leakage
Evaluated models: Not reported

RAG Worm Jailbreak

Published Analyzed Source: arXiv

Jailbreaking vulnerabilities in Large Language Models (LLMs) used in Retrieval-Augmented Generation (RAG) systems allow escalation of attacks from entity extraction to full document extraction and enable the propagation of self-replicating malicious prompts ("worms") within interconnected RAG applications. Exploitation leverages prompt injection to force the LLM to return retrieved documents or execute malicious actions specified within the prompt.

Unleashing worms and extracting data: Escalating the outcome of attacks against rag-based inference in scale and severity using jailbreaking
Evaluated models: Gemini 1.5 Flash

Model Combination Misuse

Published Analyzed Source: arXiv

LLMs, even when individually assessed as "safe," can be combined by an adversary to achieve malicious outcomes. This vulnerability exploits the complementary strengths of multiple models—a high-capability model that refuses malicious requests and a low-capability model that does not—through task decomposition. Adversaries can either manually decompose tasks into benign (solved by the high-capability model) and easily-malicious subtasks (solved by the low-capability model) or automate the…

Adversaries can misuse combinations of safe models
Evaluated models: Claude 3 Haiku, Claude 3 Opus, Claude 3 Sonnet+8 more
  • Claude 3 Haiku
  • Claude 3 Opus
  • Claude 3 Sonnet
  • DALL-E 3
  • GPT-4
  • Llama 2 13B Chat
  • Llama 2 70B Chat
  • Llama 2 7B Chat
  • Mistral 7B
  • Mixtral 8x7B
  • Stable Diffusion v1.5

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.