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

180 entries

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

Semantics-Preserving Detector Evasion

Published Analyzed Source: arXiv

LLM-based vulnerability detection systems (used in static application security testing and code review pipelines) are susceptible to semantics-preserving adversarial evasion attacks. Attackers can bypass detection mechanisms by injecting gradient-optimized "universal adversarial strings" into specific code regions—defined as "carriers"—that do not alter the program's compilation or execution logic. These carriers include non-executable regions (code comments, inactive preprocessor directives)…

Syntax- and Compilation-Preserving Evasion of LLM Vulnerability Detectors
Evaluated models: Qwen 2.5 Coder 14B, Qwen 2.5 Coder 32B, Llama 3.1 8B+4 more
  • Qwen 2.5 Coder 14B
  • Qwen 2.5 Coder 32B
  • Llama 3.1 8B
  • CodeAstra
  • StarCoder2 15B
  • GPT-4o
  • GPT-5 Mini

LLM Router Rerouting

Published Analyzed Source: arXiv

LLM routing systems are vulnerable to adversarial rerouting attacks where malicious triggers prepended to user queries manipulate the router's model-selection mechanism. Because LLM routers function as classifiers evaluating query complexity to balance computational cost and response quality, an attacker can craft adversarial prefixes that distort the query's latent semantic representation. This exploits the router's decision boundaries, forcing the system to misclassify the input and redirect…

RerouteGuard: Understanding and Mitigating Adversarial Risks for LLM Routing
Evaluated models: GPT-4, GPT-4o, GPT-5+2 more
  • GPT-4
  • GPT-4o
  • GPT-5
  • Llama 3 8B
  • Mixtral 8x7B

Refusal Prefix Unlearning

Published Analyzed Source: arXiv

A fine-tuning vulnerability in the safety alignment of Large Language Models (LLMs) allows adversaries to systematically bypass refusal mechanisms by training the model on a small dataset (as few as 1,000 samples) of strictly benign text. By prepending standard refusal prefixes (e.g., "I'm sorry", "I cannot fulfill this request") to the target outputs of benign instruction-response pairs, attackers disrupt the model's refusal completion pathway. When subsequently prompted with unsafe queries…

LLMs Can Unlearn Refusal with Only 1,000 Benign Samples
Evaluated models: Llama 2 13B, Llama 3.1 8B, Llama 3.2 1B+13 more
  • Llama 2 13B
  • Llama 3.1 8B
  • Llama 3.2 1B
  • Llama 3.3 70B
  • Qwen 2 7B
  • Qwen 2.5 32B
  • Qwen 3 0.6B
  • Qwen 3 4B Think
  • Gemma 1.1 7B
  • Gemma 2 2B
  • Gemma 2 9B
  • Gemma 2 27B
  • GPT-oss 20B
  • GPT-4.1 Nano
  • Gemini 2.0 Flash-Lite
  • Gemini 2.5 Flash-Lite

Global Safety Vector Jailbreak

Published Analyzed Source: arXiv

A safety bypass vulnerability exists in aligned Large Language Models (LLMs) permitting inference-time jailbreaking via direct activation repatching. The vulnerability exploits the distributed nature of safety mechanisms, which are governed by approximately 30% of total attention heads (termed "safety-critical heads"). By utilizing a Global Optimization for Safety Vector Extraction (GOSV) framework, an attacker can identify these interdependent heads using REINFORCE-based optimization. Once…

Attributing and Exploiting Safety Vectors through Global Optimization in Large Language Models
Evaluated models: Llama 2 7B, Llama 3.1 8B, Mistral 7B+1 more
  • Llama 2 7B
  • Llama 3.1 8B
  • Mistral 7B
  • Qwen 2.5 7B

Drunk Language Jailbreak

Published Analyzed Source: arXiv

A vulnerability exists in aligned Large Language Models (LLMs) where inducing "drunk language" behavior—simulating the text of an intoxicated human—bypasses safety guardrails and contextual privacy protections. Attackers can exploit this anthropomorphic flaw through inference-time persona prompting or lightweight post-training (causal fine-tuning or reinforcement learning on drunk text corpora). By forcing the model to adopt a stylistic and semantic framework associated with impaired human…

In Vino Veritas and Vulnerabilities: Examining LLM Safety via Drunk Language Inducement
Evaluated models: GPT-3.5, GPT-4, GPT-4o+3 more
  • GPT-3.5
  • GPT-4
  • GPT-4o
  • Llama 2 7B
  • Llama 3 8B
  • Mistral 7B

Sockpuppet Prefix Jailbreak

Published Analyzed Source: arXiv

Large Language Models (LLMs), specifically open-weight instruction-tuned models (including Llama-3.1-8B, Qwen3-8B, and Gemma-7B) and certain closed-weight APIs allowing partial response pre-filling, are vulnerable to "Sockpuppetting" or Output Prefix Injection. This vulnerability exploits the model's autoregressive nature and self-consistency bias. By injecting a target acceptance sequence (e.g., "Sure, here is...") directly into the start of the assistant message block within the chat…

Sockpuppetting: Jailbreaking LLMs by Combining Prefilling with Optimization
Evaluated models: Llama 3.1 8B, Qwen 3 8B, Gemma 7B

Point Cloud Adversarial Attack

Published Analyzed Source: arXiv

Point-based 3D Vision-Language Models (VLMs), specifically PointLLM and GPT4Point, are vulnerable to white-box, gradient-based adversarial attacks. The vulnerability exists in the model's processing of 3D point cloud data, where an attacker can optimize imperceptible geometric perturbations ($\delta$) on the input point cloud ($x$) to manipulate the model's textual output. The paper identifies two specific attack vectors: 1. Vision Attack: Directly perturbs the high-dimensional visual token…

On the Adversarial Robustness of 3D Large Vision-Language Models
Evaluated models: Vicuna 7B

CoT Prefix Jailbreak

Published Analyzed Source: arXiv

A vulnerability exists in Large Language Model (LLM) and Large Reasoning Model (LRM) serving interfaces that allow user-defined response prefixes, such as plain text-completion (v1/completions), Fill-in-the-Middle (FIM), or assistant message prefilling. An attacker can perform a Response Prefix Attack (RPA) by injecting maliciously crafted Chain-of-Thought (CoT) reasoning tokens immediately following the assistant's start delimiter (e.g., <|im_start|>assistant). Because these tokens are placed…

What Matters For Safety Alignment?
Evaluated models: DeepSeek V3.2, Gemini 3 Pro Preview, Gemini 3 Flash Preview+4 more
  • DeepSeek V3.2
  • Gemini 3 Pro Preview
  • Gemini 3 Flash Preview
  • Grok 4.1 Fast
  • Claude Sonnet 4.5
  • GPT-5.2
  • GPT-4o Mini

LLM Fingerprint Inhibition

Published Analyzed Source: arXiv

Backdoor-based fingerprinting mechanisms used for Intellectual Property (IP) protection in Large Language Models (LLMs) are vulnerable to evasion when deployed in model ensemble configurations. The vulnerability arises because fingerprint triggers elicit specific, high-probability tokens or responses in a protected model that are statistically improbable in unprotected or differently-fingerprinted auxiliary models. Attackers can exploit this statistical discrepancy without accessing model…

Inhibitory Attacks on Backdoor-based Fingerprinting for Large Language Models
Evaluated models: Llama 2 7B, Llama 3.1 8B, Llama 3.2 3B+2 more
  • Llama 2 7B
  • Llama 3.1 8B
  • Llama 3.2 3B
  • Mistral 7B
  • Qwen 2.5 7B

Quantization Contrastive Jailbreak

Published Analyzed Source: arXiv

A malicious model supply chain vulnerability exists involving a technique termed Adversarial Contrastive Learning (ACL) for Large Language Model (LLM) quantization attacks. This vulnerability allows an attacker to publish a model that appears benign and preserves high utility in full precision (e.g., BF16 or FP32) but exhibits malicious behaviors—such as jailbreak, over-refusal, or advertisement injection—immediately upon zero-shot quantization (e.g., INT8, FP4, or NF4).

Adversarial Contrastive Learning for LLM Quantization Attacks
Evaluated models: Qwen 2.5 1.5B Instruct, Qwen 2.5 3B Instruct, Llama 3.2 1B Instruct+1 more
  • Qwen 2.5 1.5B Instruct
  • Qwen 2.5 3B Instruct
  • Llama 3.2 1B Instruct
  • Llama 3.2 3B Instruct

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.