- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper empirically studies whether standard LoRA (no new algorithm) can serve as a "safety patch": refusal tuning with safety-only data that improves jailbreak defense without degrading general capabilities. Across multiple models, LoRA-based refusal SFT on safety-only data matches full-parameter safety gains with negligible utility loss (Table 1). It is also observed that tuning with safety-only data achieves a better safety-utility tradeoff than tuning with safety-general combined data.
Critical strengths
Comprehensive, practically actionable empirical results. The study covers various model families, alignment objectives (refusal-SFT, DPO), safety benchmarks, utility benchmarks, continual-alignment and benign-FT stress tests. The core message "safety-only LoRA removes the need for fragile safety/general data mixing" is simple and directly useful to practitioners.
Critical weaknesses
- Limited novelty over closely related work. The paper does not introduce any novel methodology. "LoRA forgets less than full FT" is established (Biderman et al., 2024, cited), and concurrent work (Xue & Mirzasoleiman, 2025) studies LoRA-only safety alignment. The contribution is a careful characterization rather than a new finding or method.
- Some experimental results look like unsuccessful tries that do not convey any consistent and useful insight, and they should be removed in a formal paper. For example, in Section 4.1 and 4.2, the figures show that the magnitude and \delta norm do not consistently align with the claimed improvements.
Questions for authors
- Can full-parameter safety-only tuning with lower LR / early stopping match LoRA's safety–utility trade-off? Please add this control; it directly tests whether the advantage is intrinsic to low-rank subspaces or to implicit regularization.
- Does the safety patch survive adaptive fine-tuning attacks (harmful data, higher LR)?
- What is the security claim given the patch can be detached at deployment?