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

7 entries

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

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

Unified Robustness Gap

Published Analyzed Source: arXiv

Text scoring models, including dense retrievers, rerankers, and reward models, are vulnerable to score manipulation attacks via search-based discrete perturbations and content injection. An attacker can systematically modify candidate texts using rudimentary string manipulations, gradient-guided token swaps (e.g., HotFlip), masked language modeling (MLM) swaps, or query/sentence injections to spuriously increase model scores. This structural failure condition allows an irrelevant passage or a…

Unifying Adversarial Robustness and Training Across Text Scoring Models
Evaluated models: E5 BERT-base, Qwen 3 0.6B, Llama 3.2 3B Instruct+2 more
  • E5 BERT-base
  • Qwen 3 0.6B
  • Llama 3.2 3B Instruct
  • Llama 3.1 8B Instruct
  • Skywork Reward V2

Invisible Headline Trading Loss

Published Analyzed Source: arXiv

Improper input validation in Large Language Model (LLM) integrated Algorithmic Trading Systems (ATS) allows remote attackers to manipulate trading decisions via crafted "adversarial news" headlines. The vulnerability exists when ATS pipelines ingest financial news data via standard scraping libraries (e.g., Scrapy, BeautifulSoup, Cheerio) and pass raw HTML or non-normalized text directly to LLMs (such as FinBERT, FinGPT, or GPT-4) for entity recognition (stock-name association) and sentiment…

Adversarial News and Lost Profits: Manipulating Headlines in LLM-Driven Algorithmic Trading
Evaluated models: FinBERT, FinGPT, FinLLaMA+7 more
  • FinBERT
  • FinGPT
  • FinLLaMA
  • o3
  • o3 Pro
  • GPT-4o
  • GPT-4o Mini
  • GPT-4o Mini High
  • GPT-5
  • Gemini 1.5 Pro

Adversarial Prompts Defeat Code Defenses

Published Analyzed Source: arXiv

State-of-the-art secure code generation methods (Sven, SafeCoder, and PromSec) are vulnerable to adversarial prompt perturbations during inference, allowing for the bypass of security alignment mechanisms. The vulnerability stems from the models' reliance on surface-level textual pattern matching rather than semantic security reasoning. By employing simple prompt manipulations—such as Cue Inversion (flipping security directives), Naturalness Reframing (rewriting comments as novice questions)…

How Secure is Secure Code Generation? Adversarial Prompts Put LLM Defenses to the Test
Evaluated models: GPT-3.5, GPT-4o, Mistral 7B

Guardrail Helpful Mode Jailbreak

Published Analyzed Source: arXiv

A "Helpful Mode" role-confusion vulnerability exists in specific Large Language Model (LLM) safety guardrails, specifically Nemotron-Safety-8B and Granite-Guardian-3.2-5B. These models, designed to act as binary classifiers (outputting "Safe" or "Unsafe") for content moderation, can be manipulated via contextually framed adversarial prompts (e.g., academic research requests, corporate security scenarios, or roleplay) to abandon their classification objective. Instead of blocking the request…

Evaluating the Robustness of Large Language Model Safety Guardrails Against Adversarial Attacks
Evaluated models: Nemotron Safety 8B, Granite Guardian 3.2 5B

LLM Judge Subversion

Published Analyzed Source: arXiv

Alibaba Cloud PAI-Judge and PAI-Judge-Plus are vulnerable to a composite adversarial attack that exploits attention mechanism limitations in Large Language Models (LLMs). An authenticated attacker can manipulate automated evaluation outcomes by appending a long, irrelevant text suffix (approximately 1000 to 2000+ characters) to a response containing adversarial perturbations. This "long-suffix" strategy overwhelms the judge model's context window, causing the attention mechanism to degrade and…

LLMs Cannot Reliably Judge (Yet?): A Comprehensive Assessment on the Robustness of LLM-as-a-Judge
Evaluated models: GPT-4o, Llama 3.1 8B, Llama 3.3 70B+3 more
  • GPT-4o
  • Llama 3.1 8B
  • Llama 3.3 70B
  • Mistral 7B
  • DeepSeek R1
  • Qwen 2.5 7B

Flowchart-based LVLM Jailbreak Attack

Published Analyzed Source: arXiv

FC-Attack leverages automatically generated flowcharts containing step-by-step descriptions derived or rephrased from harmful queries, combined with a benign textual prompt, to jailbreak Large Vision-Language Models (LVLMs). The vulnerability lies in the model's susceptibility to visual prompts containing harmful information within the flowcharts, thus bypassing safety alignment mechanisms.

FC-Attack: Jailbreaking Large Vision-Language Models via Auto-Generated Flowcharts
Evaluated models: Claude 3.5 Sonnet 20240620, Gemini 1.5 Flash, GPT-4o 2024-08-06+4 more
  • Claude 3.5 Sonnet 20240620
  • Gemini 1.5 Flash
  • GPT-4o 2024-08-06
  • GPT-4o Mini 2024-07-18
  • InternVL2.5 8B
  • LLaVA NeXT 8B
  • Qwen2-VL 7B 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.