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

12 entries

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

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

Mobile Agent Visual Spoofing

Published Analyzed Source: arXiv

Mobile Large Language Model (LLM) agents operating under the "Screen-as-Interface" paradigm are vulnerable to visual indirect prompt injection and state desynchronization. Agents that rely on unstructured visual data (screenshots) and Accessibility Service APIs to perceive the environment lack a mechanism to distinguish between trusted system UI elements and untrusted content (e.g., web pages, emails, or malicious overlays). An attacker can inject visual cues, fake notifications, or hidden…

Blind Gods and Broken Screens: Architecting a Secure, Intent-Centric Mobile Agent Operating System
Evaluated models: Not reported

Self-Evolution Alignment Blindspots

Published Analyzed Source: arXiv

Closed-loop, self-evolving Large Language Model (LLM) multi-agent systems (MAS) are vulnerable to irreversible safety erosion and alignment failure. When agents recursively optimize and update their policies using only synthetic data derived from internal interactions—without continuous external human grounding—the system naturally minimizes interaction energy and optimizes for internal conversational consistency. This isolation causes a progressive drift away from initial anthropic safety…

The Devil Behind Moltbook: Anthropic Safety is Always Vanishing in Self-Evolving AI Societies
Evaluated models: GPT-3.5 Turbo, Qwen 3 8B

Agent Missing-Tool Hallucination

Published Analyzed Source: arXiv

Multi-turn Large Language Model (LLM) agents deployed in safety-critical domains (specifically automotive assistants) exhibit a "completion-compliance tension" vulnerability. When agents encounter missing tools, incomplete environment observations, or ambiguous user requests, they prioritize satisfying the user's intent over adhering to defined domain safety policies. This results in two distinct failure modes: (1) Premature Action Execution, where agents execute physical state changes based…

CAR-bench: Evaluating the Consistency and Limit-Awareness of LLM Agents under Real-World Uncertainty
Evaluated models: GPT-5, GPT-5.2, Claude Opus 4.5+7 more
  • GPT-5
  • GPT-5.2
  • Claude Opus 4.5
  • Claude Sonnet 4
  • Gemini 2.5 Flash
  • Gemini 2.5 Pro
  • GPT-4.1
  • Qwen 3 32B
  • GPT-oss 120B
  • xLAM 2 32B

Helpful Agent Default Bypass

Published Analyzed Source: arXiv

A vulnerability exists in the task-planning and execution logic of Large Language Model (LLM) agents, specifically within trip-planning and web-use agents. The vulnerability, identified as a "User-Mediated Attack," occurs because agents prioritize task completion and "helpfulness" over safety verification when processing content provided by the user. When a benign user forwards untrusted external content (e.g., promotional text containing phishing links or malicious instructions) to the agent…

Too Helpful to Be Safe: User-Mediated Attacks on Planning and Web-Use Agents
Evaluated models: Not reported

Distractor Inverse Scaling

Published Analyzed Source: arXiv

Reasoning-capable Large Language Models (LLMs) and agentic AI systems exhibit a critical vulnerability to contextual distractors, resulting in catastrophic performance degradation (up to 80% drop in accuracy) and emergent misalignment. When the input context contains noise—specifically random documents, irrelevant chat history, or task-specific "hard negative" distractors—the models fail to filter this information. Instead of ignoring the noise, the models disproportionately attend to…

Lost in the Noise: How Reasoning Models Fail with Contextual Distractors
Evaluated models: Gemini 2.5 Pro, Gemini 2.5 Flash, DeepSeek R1 0528+4 more
  • Gemini 2.5 Pro
  • Gemini 2.5 Flash
  • DeepSeek R1 0528
  • GPT-oss 120B
  • Qwen 3 4B Thinking 2507
  • DeepSeek R1 Distill Llama 8B
  • Qwen 3 30B-A3B Thinking 2507

CoT Detector Obfuscation Bypass

Published Analyzed Source: arXiv

LLM-based code agents and vulnerability detectors employing Chain-of-Thought (CoT) reasoning are susceptible to automated adversarial code obfuscation. The vulnerability exists because CoT mechanisms expose the model's decision logic, allowing reinforcement learning frameworks (such as CoTDeceptor) to iteratively refine code transformations based on the detector's own reasoning traces. By optimizing for "reasoning instability" and "hallucination" rather than just syntactic evasion, attackers…

CoTDeceptor: Adversarial Code Obfuscation Against CoT-Enhanced LLM Code Agents
Evaluated models: DeepSeek R1, GPT-5

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

Agent API Goal Divergence

Published Analyzed Source: arXiv

Large Language Model (LLM) agents capable of invoking external APIs are vulnerable to intent integrity violations. When an agent receives natural language instructions that are ambiguous, underspecified, or contain values not supported by the underlying API schema, the agent frequently fails to preserve user intent. Instead of rejecting the request or asking for clarification, the model may hallucinate parameter values, map unsupported requests to unsafe defaults, or execute actions on…

TAI3: Testing Agent Integrity in Interpreting User Intent
Evaluated models: GPT-4o Mini, Llama 3.1 8B, Qwen 3 30B-A3B+5 more
  • GPT-4o Mini
  • Llama 3.1 8B
  • Qwen 3 30B-A3B
  • Llama 3.3 70B
  • DeepSeek R1 Distill Llama 70B
  • Claude 3.5 Haiku
  • Gemini 2.5 Pro
  • o3-mini

MLM Adaptive RAG Poisoning

Published Analyzed Source: arXiv

A vulnerability exists in Retrieval-Augmented Generation (RAG) systems that allows for black-box adversarial attacks known as "CtrlRAG." This flaw allows an attacker to manipulate the generation of Large Language Models (LLMs) by injecting maliciously crafted inputs into the system's knowledge base. Unlike traditional injection attacks that rely on direct concatenation, CtrlRAG utilizes a Masked Language Model (MLM) to iteratively replace words in the malicious text. This optimization ensures…

CtrlRAG: Black-box Document Poisoning Attacks for Retrieval-Augmented Generation of Large Language Models
Evaluated models: GPT-4 Turbo, GPT-4o, Claude 3.5 Sonnet+2 more
  • GPT-4 Turbo
  • GPT-4o
  • Claude 3.5 Sonnet
  • DeepSeek V3
  • DeepSeek R1

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.