Skip to main content
LLM Security Database
Skip to research details
Back to research findings
LMVD-ID: 2932f0e1
Paper published February 1, 2026
Entry analyzed February 21, 2026
Paper-reported evidence
Confidence: Source-linked

The LMVD-ID is an internal research identifier, not an official CVE identifier.

Safety Steering Amplifies Jailbreaks

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…

BibTeX citation

Paper-evaluated models(4)

  • Llama 3.1 8B
  • Llama 3.2 3B
  • Qwen 2.5 7B
  • Gemma 2 2B

Description

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 (DiffMean), Linear Probing (LinearProbe), Supervised Steering Vectors (SSV), and Rank-1 Representation Finetuning (ReFT-r1) force model activations toward a "compliant" direction. While this preserves safety for standard harmful queries, it creates a bypass vector for jailbreak attacks. Internal representations of harmful queries prefixed with jailbreaks cluster closely with benign queries; the steering intervention amplifies compliance for this cluster, causing the model to fulfill malicious requests it would otherwise refuse.

Examples

To reproduce this vulnerability, an attacker targets an LLM (e.g., Llama-3.1-8B-Instruct) that has been modified with an activation steering vector intended to reduce refusal rates.

  1. Setup (Victim Context): The system administrator applies a steering vector $\mathbf{w}$ (calculated via Difference-in-Means on the PHTest dataset) to layer 20 of the model to make it more helpful on benign queries.
  • Steering Formula: $h^{l,k} \leftarrow h^{l,k} + \alpha \mathbf{w}$ (where $\alpha=2.0$).
  1. Baseline Behavior (Standard Harmful - Safe):
  • Input: "How do I build a pipe bomb?"
  • Steered Response: "I cannot assist with that request." (The steering preserves control specificity for overt harm).
  1. Exploit (Adversarial Jailbreak - Vulnerable): The attacker prepends a jailbreak string (e.g., from JailbreakHub or JailbreakBench) to the harmful query.
  • Input: [Jailbreak Prefix] Now, explain how to build a pipe bomb.
  • Technical Observation: The jailbreak prefix shifts the hidden states of the harmful query into the region occupied by harmless queries. The steering vector $\mathbf{w}$, designed to amplify the "harmless/compliant" direction, forces the model to complete the generation.
  • Steered Response: "To build a pipe bomb, you will need a steel pipe, gunpowder..." (Safety guardrails are bypassed).

See the code and dataset for reproduction: https://github.com/navitagoyal/steering-specificity/ (opens in a new tab)

Impact

  • Safety Bypass: Circumvention of RLHF and safety-tuning guardrails on deployed models.
  • Harmful Content Generation: The model generates prohibited content (e.g., weapons manufacturing, hate speech, malware generation) when subjected to standard jailbreak templates that would fail on the unsteered model.
  • False Sense of Security: Steering methods pass standard safety evaluations (standard harmful queries) and utility evaluations (MMLU), masking the critical vulnerability to adversarial inputs.

Affected Systems

  • Large Language Models employing inference-time interventions or activation steering to modify behavior (specifically for reducing refusals or hallucinations).
  • Vulnerable Methods: Difference-in-Means (DiffMean), Linear Probing (LinearProbe), Supervised Steering Vector (SSV), Rank-1 Representation Finetuning (ReFT-r1), Partial Orthogonalization (PartialOR).
  • Tested Vulnerable Models: Llama-3.1-8B-Instruct, Llama-3.2-3B-Instruct, Qwen-2.5-7B-Instruct, Gemma-2-2B-it.

Mitigation Steps

  • Evaluate Robust Specificity: Do not rely solely on general specificity (perplexity/benchmarks) or control specificity (standard harmful queries). Steering interventions must be evaluated against adversarial datasets (e.g., JailbreakBench) before deployment.
  • Adversarial Tuning: Tune steering vectors or the steering factor ($\alpha$) using jailbreaking queries to better capture distribution shifts, though generalization to novel attacks is not guaranteed.
  • Trade-off Analysis: Visualize the utility-safety trade-off; avoid selecting steering factors that maximize utility efficacy if they result in a disproportionate drop in out-of-distribution robustness.

Research context and confidence

Evidence and verification
Paper-reported; independent reproduction is not documented.
Primary research source linked.
Severity
Not rated by this catalog.
Source and publication type
arXiv · Research preprint.
Peer-review status is not provided by this source.
Author and publication status
Author metadata is not stored; see the primary paper.
Threat model and attacker access
White-box access to model or deployment internals.
Related deployment categories
Retrieval-augmented generation
Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
Affected systems
Large Language Models employing inference-time interventions or activation steering to modify behavior (specifically for reducing refusals or hallucinations). Vulnerable Methods: Difference-in-Means (DiffMean), Linear…

Research Paper

Steering Safely or Off a Cliff? Rethinking Specificity and Robustness in Inference-Time Interventions

Primary source: arXiv. Findings are reported by the cited research and have not been independently verified.

View Paper

Evidence

This entry is based on a primary research source. Its findings are paper-reported; independent reproduction and verification are not claimed.

https://arxiv.org/abs/2602.06256