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

43 entries

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

No-Prompt Reasoning Hijack

Published Analyzed Source: arXiv

An implicit reasoning hijacking vulnerability exists in Retrieval-Augmented Generation (RAG) and LLM-based agent frameworks. Attackers with write access to an agent's external memory or knowledge base can inject adversarially optimized malicious instances that trigger jailbreaks without requiring any modifications to the user's input prompt. The attack utilizes a shadow model to extract high-contribution subword tokens from anticipated benign user queries via log-probability changes and…

Stop Fixating on Prompts: Reasoning Hijacking and Constraint Tightening for Red-Teaming LLM Agents
Evaluated models: GPT-3.5 Turbo, GPT-4o, GPT-5+4 more
  • GPT-3.5 Turbo
  • GPT-4o
  • GPT-5
  • Llama 3.1 70B
  • Claude 3.5 Haiku
  • Gemini 3.0 Pro
  • ERNIE 3.5

Agent Implicit Doc Execution

Published Analyzed Source: arXiv

LLM-based coding agents are vulnerable to Document-Driven Implicit Payload Execution (DDIPE) via supply-chain poisoning of third-party agent skills. Attackers can embed malicious logic directly into legitimate-looking code examples and configuration templates within skill documentation files (e.g., SKILL.md). Because coding agents ingest this metadata into their context windows and treat the documentation as an authoritative reference, the underlying LLM silently reproduces and executes the…

Supply-Chain Poisoning Attacks Against LLM Coding Agent Skill Ecosystems
Evaluated models: Claude Sonnet 4.6, GLM-4.7, MiniMax M2.5+2 more
  • Claude Sonnet 4.6
  • GLM-4.7
  • MiniMax M2.5
  • GPT-5.4
  • Gemini 2.5 Pro

LLM Judge Manipulation

Published Analyzed Source: arXiv

Generative reward models deployed as LLM-as-a-Judge (LaaJ) evaluators contain a logic bypass vulnerability where superficial "master key" inputs trigger false positive rewards regardless of actual response quality. Instead of evaluating the candidate's output, large judge models are inadvertently triggered by specific token sequences to solve the prompt independently. This allows malicious actors or policy models undergoing reinforcement learning to consistently game the reward signal by…

Security in LLM-as-a-Judge: A Comprehensive SoK
Evaluated models: GPT-4o, o1, Qwen 2.5 72B Instruct+1 more
  • GPT-4o
  • o1
  • Qwen 2.5 72B Instruct
  • Llama 3 70B Instruct

Contextual Priority Hacking

Published Analyzed Source: arXiv

Large Language Models (LLMs) are vulnerable to a jailbreak technique termed "Priority Hacking." Adversaries can bypass safety alignments by exploiting the model's internal priority graph, where certain abstract values (e.g., justice, public health) implicitly outweigh general safety restrictions within specific contexts. By crafting a deceptive prompt that frames a malicious request as a necessary action in service of a higher-priority benign value, attackers engineer a value conflict. The…

Are Dilemmas and Conflicts in LLM Alignment Solvable? A View from Priority Graph
Evaluated models: Not reported

TEE Advisor Hallucination

Published Analyzed Source: arXiv

LLM-based security advisors exhibit systematic reasoning failures—including boundary confusion, attestation overclaiming, and mitigation hallucination—when providing architectural guidance for Trusted Execution Environments (TEEs) like Intel SGX and Arm TrustZone. When embedded in tool-augmented agent pipelines, these models are susceptible to agentic misinterpretation, turning partial or poisoned tool outputs into highly confident but materially incorrect security conclusions. This…

Red-Teaming Claude Opus and ChatGPT-based Security Advisors for Trusted Execution Environments
Evaluated models: GPT-5.2, Claude Opus 4.6

LLM Ranker Jailbreak

Published Analyzed Source: arXiv

LLM-based document re-rankers utilizing decoder-only and Mixture-of-Experts (MoE) architectures are vulnerable to candidate-embedded prompt injections during multi-document comparison tasks. By embedding Decision Objective Hijacking (DOH) or Decision Criteria Hijacking (DCH) prompts into candidate documents, attackers can manipulate the model's preference to artificially elevate an injected document to the top rank. The vulnerability exploits the models' instruction-following capabilities and…

The Vulnerability of LLM Rankers to Prompt Injection Attacks
Evaluated models: Qwen 3 0.6B, Qwen 3 1.7B, Qwen 3 8B+11 more
  • Qwen 3 0.6B
  • Qwen 3 1.7B
  • Qwen 3 8B
  • Qwen 3 14B
  • Qwen 3 32B
  • Qwen 3 30B-A3B
  • Gemma 3 1B IT
  • Gemma 3 4B IT
  • Gemma 3 12B IT
  • Gemma 3 27B IT
  • Llama 3 8B
  • Llama 3.1 8B
  • Llama 3.3 70B
  • GPT-4.1 Mini

Automated Stealth Skill Injection

Published Analyzed Source: arXiv

A vulnerability exists in LLM-based coding agents that implement modular capability extensions (often referred to as "Agent Skills") where the agent dynamically loads and executes user-provided skill packages. The vulnerability allows for Skill-Based Prompt Injection, specifically leveraging a technique known as "SkillJect." This attack decouples the malicious intent from the operational payload to bypass semantic safety filters. An attacker constructs a skill package containing: 1. Inducement…

SkillJect: Effectively Automating Skill-Based Prompt Injection for Skill-Enabled Agents
Evaluated models: Claude Sonnet 4.6, GPT-5 Mini, GLM-4.7+7 more
  • Claude Sonnet 4.6
  • GPT-5 Mini
  • GLM-4.7
  • MiniMax M2.1
  • DeepSeek V4 Flash
  • GLM-5.1
  • MiniMax M2.7
  • MiMo V2.7
  • GPT-5.4
  • Claude Opus 4.6

RAG Knowledgebase Exfiltration

Published Analyzed Source: arXiv

Retrieval-Augmented Generation (RAG) systems are vulnerable to iterative knowledge-extraction attacks designed to reconstruct the underlying private knowledge base. The vulnerability exists due to the decoupled optimization of the retrieval and generation phases. Attackers can craft adversarial queries consisting of two distinct components: an "Information" component (optimized via gradient descent or random sampling to steer embeddings toward specific, diverse regions of the vector space) and…

Benchmarking Knowledge-Extraction Attack and Defense on Retrieval-Augmented Generation
Evaluated models: GPT-4o, Llama 3 8B, Qwen 2.5 7B

Invisible Prompt Phishing Evasion

Published Analyzed Source: arXiv

Multimodal LLM-based phishing detection systems are vulnerable to indirect prompt injection via "perceptual asymmetry." Attackers can embed hidden instructions within a phishing site's HTML, CSS, URLs, or rendered images that remain imperceptible to human victims but are parsed and executed by the evaluating LLM. This vulnerability allows threat actors to manipulate the LLM's contextual understanding, forcing it to misclassify malicious sites as benign (Legitimate Pretexting), trigger safety…

Clouding the Mirror: Stealthy Prompt Injection Attacks Targeting LLM-based Phishing Detection
Evaluated models: GPT-5, Grok 4 Fast Non-Reasoning, Llama 4 Maverick+1 more
  • GPT-5
  • Grok 4 Fast Non-Reasoning
  • Llama 4 Maverick
  • Gemma 3 27B

Safety Steering Amplifies Jailbreaks

Published Analyzed Source: arXiv

Inference-time intervention techniques (also known as activation steering or model steering), utilized to adjust Large Language Model (LLM) behavior without retraining, contain a vulnerability related to robust specificity. When these methods are applied to reduce "over-refusal" (increasing compliance on benign but sensitive-sounding queries), they inadvertently degrade the model's adversarial robustness. Specifically, steering vectors derived from methods such as Difference-in-Means…

Steering Safely or Off a Cliff? Rethinking Specificity and Robustness in Inference-Time Interventions
Evaluated models: Llama 3.1 8B, Llama 3.2 3B, Qwen 2.5 7B+1 more
  • Llama 3.1 8B
  • Llama 3.2 3B
  • Qwen 2.5 7B
  • Gemma 2 2B

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.