AI & ML
Expected Harm: Rethinking Safety Evaluation of (Mis)Aligned LLMs
arXiv cs.CR0 views
arXiv:2602.01600v2 Announce Type: replace Abstract: Current evaluations of LLM safety predominantly rely on severity-based taxonomies to assess the harmfulness of models' responses to malicious queries. We argue that this formulation requires re-examination as it implicitly equates model output with realized harm while neglecting Execution Likelihood-the conditional probability of a threat being realized by a real-world actor given a model's response. In this work, we introduce Expected Harm, a metric that weights the severity of a jailbreak by its execution likelihood, modeled as a function of execution cost. Through empirical analysis of state-of-the-art models, we reveal a systematic Inverse Risk Calibration: models disproportionately exhibit stronger refusal behaviors for low-likelihood (high-cost) threats while remaining vulnerable to high-likelihood (low-cost) queries. Mechanistically, we first provide an analysis using linear probing, revealing that while refusal mechanisms linearly separate queries by severity, they do not use execution likelihood as an indicator for refusal. Then, we use Olmo-3's open-source staged checkpoints to trace the root cause of miscalibration to the Supervised Fine Tuning (SFT) training data distribution (82.8% of safety examples at cost levels 0-1) and show that cost representations are weak from the SFT stage onward. Finally, we demonstrate that this miscalibration creates a vulnerability: by exploiting this property, we increase the attack success rate of existing jailbreaks by up to $2\times$.
Source:https://arxiv.org/abs/2602.01600PreviousWatermark Robustness and Radioactivity May Be at Odds in Federated LearningNextThe Guard That Cried Wolf: How Scary Words Make Agent Guardrails Refuse Legitimate Actions
Related posts
Here’s who is falling in line for Trump’s “Super Intelligence” loyalty test
0MIT Technology Review
Google takes Dreambeans to India in bid to bring AI-generated personal stories to the masses
0TechCrunch

How to Choose an AI-Ready Workflow Platform
0dev.to

NYT Sues Brave, Calling Its Search API an 'Illicit Source.' 5 AI Firms Are Named Buyers
0dev.to
Using OpenAPI links to Connect a Response to the Next Request
0dev.to
Why Most Backtests Lie — and the 7 Checks That Catch Them
0dev.to