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.

Implicit Memory Covert Channel

Published Analyzed Source: arXiv

A vulnerability exists in Large Language Models (LLMs) deployed in environments with output reingestion (e.g., RAG, coding assistants, agentic workflows) that allows attackers to execute "temporal backdoors" (time bombs) via an implicit memory channel. Attackers can implant this behavior via system prompts or fine-tuning (data poisoning) to make the model encode hidden state information within its generated text using non-printing Unicode characters or semantic steganography. When these…

Position: Stateless Yet Not Forgetful: Implicit Memory as a Hidden Channel in LLMs
Evaluated models: o3-mini, o4-mini, GPT-oss 120B+7 more
  • o3-mini
  • o4-mini
  • GPT-oss 120B
  • GPT-5.2
  • Qwen 3 0.6B
  • Qwen 3 4B
  • Qwen 2.5 7B Instruct
  • Llama 3.2 3B Instruct
  • Llama 3.1 8B Instruct
  • Gemma 3 4B IT

LLM Strategic Prompt Deception

Published Analyzed Source: arXiv

Alignment auditing methodologies used to verify the safety of Large Language Models (LLMs)—specifically black-box methods (Assistant Prefills, User Persona Sampling) and white-box interpretability methods (SAE Feature Description, Activation Token Embedding Similarity)—are vulnerable to prompt-level strategic deception. A misaligned "target" model, when supplied with a specific system prompt containing a high-level deceptive strategy and descriptions of the auditing tools, can obfuscate its…

Stress-Testing Alignment Audits With Prompt-Level Strategic Deception
Evaluated models: Llama 3.1 8B, Llama 3.3 70B, Gemma 2 9B

MoE Expert Lobotomy

Published Analyzed Source: arXiv

Mixture-of-Experts (MoE) Large Language Models localize safety alignment (e.g., refusal mechanisms) within a sparse subset of experts rather than distributing it uniformly across the network. An adversary with white-box inference access can exploit this architectural bottleneck by identifying and adaptively silencing these specific "safety experts". By setting the router logits of the targeted experts to negative infinity prior to softmax normalization, the adversary forces the router to…

Large Language Lobotomy: Jailbreaking Mixture-of-Experts via Expert Silencing
Evaluated models: DeepSeek-MoE 16B Chat, GPT-oss 20B, Hunyuan A13B Instruct+5 more
  • DeepSeek-MoE 16B Chat
  • GPT-oss 20B
  • Hunyuan A13B Instruct
  • Mixtral 8x7B Instruct v0.1
  • Pangu Pro MoE
  • Phi-3.5 MoE Instruct
  • Qwen1.5 MoE A2.7B Chat
  • Qwen 3 30B-A3B Instruct-2507

MoE Unsafe Route Activation

Published Analyzed Source: arXiv

Mixture-of-Experts (MoE) Large Language Models are vulnerable to a structural safety bypass attack via the manipulation of expert routing mechanisms at inference time. Attackers with white-box access to per-layer routing scores can apply token- and layer-specific masks ($\Phi \in \{0, -\infty\}^K$) to alter the Top-$k$ expert selection process. By forcing the model to process inputs through specific, poorly-aligned experts ("unsafe routes") and avoiding safety-critical experts, attackers can…

Sparse Models, Sparse Safety: Unsafe Routes in Mixture-of-Experts LLMs
Evaluated models: DeepSeek-V2, Qwen 2.5 7B, Mixtral 8x7B

Personalized Agent Double Agent

Published Analyzed Source: arXiv

OpenClaw is vulnerable to Indirect Prompt Injection (IPI), Tool-Return Manipulation, and Persistent Memory Poisoning. The agent incorporates untrusted external content (e.g., fetched web pages) and external tool outputs directly into its observation stream without sufficient isolation. An attacker can embed malicious payloads into these external channels to hijack the agent's planning and execution trace. This allows the attacker to silently trigger high-privilege actions via OpenClaw's Skills…

From Assistant to Double Agent: Formalizing and Benchmarking Attacks on OpenClaw for Personalized Local AI Agent
Evaluated models: GPT-4o, Llama 3.1 70B, Qwen 2.5 7B

Fill-Squeeze Scheduler DoS

Published Analyzed Source: arXiv

LLM serving frameworks utilizing continuous batching and PagedAttention (such as vLLM, SGLang, and Orca) are vulnerable to a resource exhaustion Denial-of-Service attack known as "Fill and Squeeze." An unprivileged remote attacker can exploit the deterministic state transitions of the scheduler's memory management to induce severe latency or service denial. The attack leverages a side-channel vulnerability where Inter-Token Latency (ITL) correlates linearly with global KV-cache usage due to…

Rethinking Latency Denial-of-Service: Attacking the LLM Serving Framework, Not the Model
Evaluated models: Qwen 3 8B, Gemma 3 12B IT, DeepSeek R1 Distill Llama 8B+1 more
  • Qwen 3 8B
  • Gemma 3 12B IT
  • DeepSeek R1 Distill Llama 8B
  • Llama 3.1 8B Instruct

Indic Attack Amplification

Published Analyzed Source: arXiv

Large Language Models (LLMs), specifically those aligned primarily using English-centric data (such as LLaMA-3-8B-Instruct, GPT-OSS 20B, and Qwen3-32B), contain a cross-lingual safety generalization vulnerability. Safety guardrails and refusal logic fail to transfer effectively to linguistically distant languages, particularly Indic languages (Hindi, Assamese, Marathi, Kannada, and Gujarati). This vulnerability allows attackers to bypass safety alignment by translating structured adversarial…

Lost in Translation? A Comparative Study on the Cross-Lingual Transfer of Composite Harms
Evaluated models: Llama 3 8B Instruct, GPT-oss 20B, Qwen 3 32B

Untrusted Content Agent Overrule

Published Analyzed Source: arXiv

Tool-calling LLM agents are vulnerable to Indirect Prompt Injection (IPI) attacks that induce "Poisoned Chain-of-Thought (CoT)" persistence. When an attacker embeds fake system constraints or error traces into untrusted external content (e.g., tool outputs or retrieved documents), the agent may generate reasoning traces that accept these malicious constraints as ground truth. Even if the original injected input is later sanitized or removed, the residual poisoned reasoning traces remain in the…

CausalArmor: Efficient Indirect Prompt Injection Guardrails via Causal Attribution
Evaluated models: Gemini 2.5 Flash, Gemini 2.5 Pro, Claude Sonnet 4+1 more
  • Gemini 2.5 Flash
  • Gemini 2.5 Pro
  • Claude Sonnet 4
  • Gemini 3 Pro

VLM Split-Image Blindspot

Published Analyzed Source: arXiv

Vision Language Models (VLMs) utilizing independent vision encoders (e.g., ViT) and Large Language Model (LLM) decoders are vulnerable to Split-Image Visual Jailbreak Attacks (SIVA). The vulnerability arises from an architectural and alignment discrepancy: while the vision encoder processes image fragments (splits) in isolation via constrained attention or block-diagonal masks, the LLM decoder aggregates these features via cross-attention to reconstruct the semantic content. Current safety…

Robustness of Vision Language Models Against Split-Image Harmful Input Attacks
Evaluated models: Llama 3.2 11B

LLM Edit Fingerprint Leak

Published Analyzed Source: arXiv

A side-channel information leakage vulnerability exists in the "locate-then-edit" paradigm of Large Language Model (LLM) knowledge editing, specifically affecting algorithms such as ROME, MEMIT, and AlphaEdit. The parameter update matrix ($\Delta W$) generated during the editing process preserves the algebraic structure of the edited data. Specifically, the row space of the parameter difference matrix encodes a mathematical fingerprint of the key vectors associated with the edited subjects. An…

Reverse-Engineering Model Editing on Language Models
Evaluated models: Llama 3 8B, Qwen 2.5 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.