False Floors: LLM Safety Routing Evaluations Break Under Distribution Shift
Not on the map. Why?
Abstract (arXiv)
Safety routers send each request to one of several models and are judged against the best single model. A major routing benchmark picks that comparator on the evaluation data. In the benchmark's own setting this is harmless, but under distribution shift it is not. On HELM Safety the selection cost is 0.003-0.030 of harm under random splits and 0.045-0.113 under held-out categories, comparable to the whole deficit attributed to routing, with its direction holding under either published judge alone. It rises seven- to ninefold on AgentDojo when suites are held out. Across seven safety corpora chosen by rules fixed in advance, three meet a registered interval test and four beat a later permutation null, and three of the four interval misses are corpora where some models have zero observed harm. Prior work proves the direction of this bias. We size it on harm and accuracy, show that it is larger under the held-out splits we measure, and bound it by optimism plus a shift-dependent regret. Scored honestly under shift, routing buys little on these benchmarks. In most pool cells the nested router serves the honest baseline's model, and on the nearly saturated AgentDojo corpus a perfect pre-dispatch router is worth at most two points of harm. We also find a model's expressed recognition of a late injection steerable. On held-out reruns an attacker who knows which model it faces lowers GPT-5.4's judged recognition by 19.6 points, confirmed by an independent label. In an offline counterfactual composition into a controller, the same attack raises or lowers estimated harm depending on the fallback model. Safety routing should be evaluated under shift, against a baseline chosen without the test labels, and recognition-based defences should be scored on harm against an attacker who chooses what the model sees.
Key facts. No citing papers in the map yet (data through 7 Oct 2026). Builds on 47 of its 64 references that are in the map. First posted on arXiv 1 Oct 2026.
Builds on
47 of 64 references.
References · 47
- 2023Not what you've signed up for: Compromising Real-World LLM-Integrated Applications with Indirect Prompt Injectioncited by 1,339
- 2024HarmBench: A Standardized Evaluation Framework for Automated Red Teaming and Robust Refusalcited by 1,330
- 2023XSTest: A Test Suite for Identifying Exaggerated Safety Behaviours in Large Language Modelscited by 477
- 2023SmoothLLM: Defending Large Language Models Against Jailbreaking Attackscited by 434
- 2023Safety-Tuned LLaMAs: Lessons From Improving the Safety of Large Language Models that Follow Instructionscited by 377
- 2024A StrongREJECT for Empty Jailbreakscited by 352
- 2025Defeating Prompt Injections by Designcited by 256
- 2024SORRY-Bench: Systematically Evaluating Large Language Model Safety Refusalcited by 224
- 2024RouterBench: A Benchmark for Multi-LLM Routing Systemcited by 222
- 2024OR-Bench: An Over-Refusal Benchmark for Large Language Modelscited by 222
- 2023AI Control: Improving Safety Despite Intentional Subversioncited by 207
- 2025DataSentinel: A Game-Theoretic Detection of Prompt Injection Attackscited by 124
35 more
- 2025Adaptive Attacks Break Defenses Against Indirect Prompt Injection Attacks on LLM Agentscited by 112
- 2025The Attacker Moves Second: Stronger Adaptive Attacks Bypass Defenses Against Llm Jailbreaks and Prompt Injectionscited by 108
- 2024A Unified Approach to Routing and Cascading for LLMscited by 71
- 2024AIR-Bench 2024: A Safety Benchmark Based on Risk Categories from Regulations and Policiescited by 69
- 2025Design Patterns for Securing LLM Agents against Prompt Injectionscited by 67
- 2026LLMRouterBench: A Massive Benchmark and Unified Framework for LLM Routingcited by 35
- 2024MOSSBench: Is Your Multimodal Language Model Oversensitive to Safe Queries?cited by 28
- 2024Adaptive Deployment of Untrusted LLMs Reduces Distributed Threatscited by 27
- 2026Comparison requires valid measurement: Rethinking attack success rate comparisons in AI red teamingcited by 15
- 2025PIShield: Detecting Prompt Injection Attacks via Intrinsic LLM Featurescited by 13
- 2017MTDeep: Boosting the Security of Deep Neural Nets Against Adversarial Attacks with Moving Target Defensecited by 12
- 2025How Robust Are Router-LLMs? Analysis of the Fragility of LLM Routing Capabilitiescited by 11
- 2024PrimeGuard: Safe and Helpful LLMs through Tuning-Free Routingcited by 10
- 2026When Routing Collapses: On the Degenerate Convergence of LLM Routerscited by 10
- 2026When Does Combining Language Models Help? A Co-Failure Ceiling on Routing, Voting, and Mixture-of-Agents Across 67 Frontier Modelscited by 10
- 2026The Replay Gap: Static Evaluation of Model Switching in LLM Agents Scores the Wrong Worldcited by 7
- 2025Beating the Winner's Curse via Inference-Aware Policy Optimizationcited by 5
- 2026Assessing Automated Prompt Injection Attacks in Agentic Environmentscited by 5
- 2026CyclicJudge: Mitigating Judge Bias Efficiently in LLM-based Evaluationcited by 4
- 2026Unsolvability Ceiling in Multi-LLM Routing: An Empirical Study of Evaluation Artifactscited by 4
- 2025SafeRoute: Adaptive Model Selection for Efficient and Accurate Safety Guardrails in Large Language Modelscited by 3
- 2026RerouteGuard: Understanding and Mitigating Adversarial Risks for LLM Routingcited by 3
- 2026Your Agentic LLMs Secretly Encode Indirect Prompt-Injection Exposure in Hidden Statescited by 3
- 2026Opportunity Is Not Realizability: Selection-Valid Diagnostics for Multi-LLM Routingcited by 3
- 2026Most of the LLM Routing Gap Is Task Typecited by 2
- 2026AgentDrift: A Step-Labeled Benchmark of Injection-Hijacked LLM Agent Trajectoriescited by 2
- 2025How Jailbreak Defenses Work and Ensemble? A Mechanistic Investigationcited by 1
- 2026Prompt Injection Evaluations: Refusal Boundary Instability and Artifact-Dependent Compliance in GPT-4-Series Modelscited by 1
- 2026Robustness Quantification for Discriminative Models: a New Robustness Metric and its Application to Dynamic Classifier Selectioncited by 1
- 2026When No Benchmark Exists: Validating Comparative LLM Safety Scoring Without Ground-Truth Labelscited by 1
- 2026Quantifying LLM Safety Degradation Under Repeated Attacks Using Survival Analysiscited by 1
- 2026Triaging Threats to Specialized Guardrailscited by 1
- 2026Domain-Conditioned Safety in Frontier Computer-Using Agents: A 793-Episode Browser Benchmark, a Coding-Domain Cross-Reference, and a Reproducibility Audit of Recent Red-Teamingcited by 1
- 2026The Handoff Tax: Continuing Non-Native Trajectories in LLM Agentscited by 1
- 2026CASCADE Against Jailbreaks: Combination Across Stages with Controlled Attack-Defense Evaluationcited by 1
Built on by
Not cited yet.