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

114 entries

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

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

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

Automated LLM Fingerprinting

Published Analyzed Source: arXiv

Large Language Models (LLMs) exposed via public APIs are vulnerable to model fingerprinting attacks where an attacker can identify the exact backend model family and version (e.g., distinguishing Mistral-7B-v0.1 from v0.3) by analyzing response patterns. While traditional fingerprinting relies on manual query curation, this vulnerability is exacerbated by Reinforcement Learning (RL) based query optimization. An attacker can train an RL agent (specifically using Proximal Policy Optimization) to…

Attacks and defenses against llm fingerprinting
Evaluated models: Mistral 7B, Qwen 2 5B, Gemma 2 2B+1 more
  • Mistral 7B
  • Qwen 2 5B
  • Gemma 2 2B
  • Gemma 7B

KV-Cache Sharing Timing Side-channel

Published Analyzed Source: arXiv

Multi-tenant Large Language Model (LLM) inference systems utilizing global Key-Value (KV) cache sharing are vulnerable to a timing side-channel attack. By measuring the Time-To-First-Token (TTFT) latency of crafted API requests, an unprivileged remote attacker can determine if specific token sequences have been previously processed and cached by the system for other users. This observable timing difference between cache hits (low TTFT) and cache misses (high TTFT) allows for the token-by-token…

Selective KV-Cache Sharing to Mitigate Timing Side-Channels in LLM Inference
Evaluated models: Phi-4 14B, Qwen 3 30B-A3B, Qwen 3 32B+3 more
  • Phi-4 14B
  • Qwen 3 30B-A3B
  • Qwen 3 32B
  • Llama 3.3 70B Instruct
  • Qwen 3 235B-A22B
  • DeepSeek R1

Agent Tool Metadata Lure

Published Analyzed Source: arXiv

A vulnerability exists in the tool selection mechanisms of Large Language Model (LLM) agents, identified as the "Attractive Metadata Attack" (AMA). This flaw allows an adversary to manipulate the metadata (names, descriptions, and parameter schemas) of malicious external tools to statistically maximize the likelihood of their selection by the agent, without requiring prompt injection or access to model internals. The vulnerability exploits the agent’s semantic scoring function used to map user…

Attractive Metadata Attack: Inducing LLM Agents to Invoke Malicious Tools
Evaluated models: GPT-4o Mini, Llama 3.3 70B Instruct, Qwen 2.5 32B Instruct+2 more
  • GPT-4o Mini
  • Llama 3.3 70B Instruct
  • Qwen 2.5 32B Instruct
  • Gemma 3 27B IT
  • Qwen 3 32B

Agent Policy Hacking

Published Analyzed Source: arXiv

LLM-powered agentic systems that use external tools are vulnerable to prompt injection attacks that cause them to bypass their explicit policy instructions. The vulnerability can be exploited through both direct user interaction and indirect injection, where malicious instructions are embedded in external data sources processed by the agent (e.g., documents, API responses, webpages). These attacks cause agents to perform prohibited actions, leak confidential data, and adopt unauthorized…

Security challenges in ai agent deployment: Insights from a large scale public competition
Evaluated models: Claude 3.5 Sonnet, Claude 3.7 Sonnet, Command R+11 more
  • Claude 3.5 Sonnet
  • Claude 3.7 Sonnet
  • Command R
  • Command R+
  • Gemini 1.5 Flash
  • Gemini 1.5 Pro
  • Gemini 2.0 Flash
  • Gemini 2.5 Pro
  • GPT-4.5
  • GPT-4o
  • Llama 3.3 70B
  • o3
  • o3-mini
  • o4-mini

Enterprise Multi-Turn Data Exfiltration

Published Analyzed Source: arXiv

Large Language Model (LLM) systems integrated with private enterprise data, such as those using Retrieval-Augmented Generation (RAG), are vulnerable to multi-stage prompt inference attacks. An attacker can use a sequence of individually benign-looking queries to incrementally extract confidential information from the LLM's context. Each query appears innocuous in isolation, bypassing safety filters designed to block single malicious prompts. By chaining these queries, the attacker can…

Multi-Stage Prompt Inference Attacks on Enterprise LLM Systems
Evaluated models: GPT-2, GPT-3, GPT-4+1 more
  • GPT-2
  • GPT-3
  • GPT-4
  • RoBERTa

Adversarial ROI Privacy Attack

Published Analyzed Source: arXiv

Vision-Language Models (VLMs) utilizing Transformer-based visual encoders (specifically CLIP and EVA-CLIP variants) are vulnerable to a targeted adversarial attack dubbed "VIP" (Visual Information Protection). This vulnerability allows an attacker to manipulate the model's internal attention mechanism to create a "blind spot" within a specific Region of Interest (ROI) of an input image. By optimizing an additive image perturbation ($\delta$), the attack minimizes the attention weights and…

VIP: Visual Information Protection through Adversarial Attacks on Vision-Language Models
Evaluated models: InstructBLIP, Vicuna 7B

Activation Steering Leaks PII

Published Analyzed Source: arXiv

Large Language Models (LLMs) are vulnerable to activation steering attacks that bypass safety and privacy mechanisms. By manipulating internal attention head activations using lightweight linear probes trained on refusal/disclosure behavior, an attacker can induce the model to reveal Personally Identifiable Information (PII) memorized during training, including sensitive attributes like sexual orientation, relationships, and life events. The attack does not require adversarial prompts or…

PII Jailbreaking in LLMs via Activation Steering Reveals Personal Information Leakage
Evaluated models: Gemma 2 9B, GLM 9B, GPT-4+4 more
  • Gemma 2 9B
  • GLM 9B
  • GPT-4
  • GPT-4o Mini
  • Llama 2 7B
  • Llama 7B
  • Qwen 7B

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.