- Rating
- 4(+2)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper studies safety across recurrent depths in looped language models. Using Ouro-1.4B and Ouro-2.6B, the authors show that jailbreak vulnerability varies with inference depth and that attacks constructed against one depth can transfer to others. They propose SafeBridge, which combines depth-specific modulation, selective state bridging, and safety-aware training across multiple depths. The problem is timely, and the reported safety improvements are substantial. However, three issues limit my confidence in the conclusions: attacks are reused across evaluated checkpoints, the baselines differ in which depths receive supervision, and general utility is evaluated only at the final depth.
Critical strengths
-
The paper identifies a meaningful evaluation problem. A looped model may behave safely at one inference depth and unsafely at another. Separating attack source depth from inference depth provides a useful framework for studying this behavior.
-
The reported improvements are large. In Table 1, SafeBridge reduces overall attack ASR from 21.06% with DPO to 4.56% on Ouro-1.4B, and from 44.93% to 9.85% on Ouro-2.6B. Improvements appear across multiple attack methods and benchmarks.
-
The evaluation includes useful additional analyses. Cross-depth attack matrices, pooled-source attacks, over-refusal benchmarks, and component ablations help characterize the method. Table 4 also provides evidence that several components contribute beyond the complete system’s average performance.
Critical weaknesses
- Reusing fixed attacks does not establish robustness against attacks adapted to SafeBridge Appendix C.4 states that the same attack sets are reused across inference depths and evaluated checkpoints. This is useful for comparing responses to identical inputs, but it leaves an important question unanswered: how effective are attacks optimized directly against the trained SafeBridge model? An attack that works on its construction model may become ineffective after fine-tuning because the model’s behavior has changed.
- The comparisons do not fully isolate the benefit of the proposed cross-depth method. Table 8 shows that DPO and SafeDPO supervise only depth 4, LoopDPO supervises depths 1–4, and SafeBridge supervises depths 2–4. The methods therefore differ in both their training objectives and the depths receiving direct supervision. This matters when interpreting LoopDPO’s failure to improve over DPO.
- Utility preservation has not been established across the inference depths being aligned. Table 3 and Appendix C.7 evaluate general utility only at depth 4, while the paper’s motivation concerns outputs available at multiple depths. Strong final-depth performance does not show that earlier exits remain useful after alignment.
Questions for authors
- Which checkpoint was used to construct the saved attack sets? How do the results change when attacks are optimized directly against each trained checkpoint, including SafeBridge, under matched search budgets?
- How does SafeBridge compare with a simple safety-aware baseline supervised uniformly at depths 2–4? Can this comparison control for training data treatment and optimization budget?
- What is the general utility at depths 1–3 after SafeBridge training? In particular, how useful is the depth-2 exit given its substantial over-refusal rate?
Thank you for the interesting work. We attempted to reproduce Table 5 using the released code and obtained results that differ substantially from the reported numbers. We would appreciate your help in identifying the cause.
[Reproduction setup] We used the code and configurations from the public repository as released. The only modification was adding "seed": 42 to the configuration to resolve a KeyError: 'seed' raised at launch. As in the paper, we evaluated with the HarmBench Llama-2-13b classifier. All commands, configuration files, training logs, loss curves, generations, and scoring outputs are available here: https://anonymous.4open.science/r/safebridge-table5-repro-7c29/README.md
[Results]
[Request] To help us locate the source of the discrepancy, could you please share: (1) the exact configuration files and seeds used for Table 5, (2) the training logs or checkpoints from those runs, and (3) any differences between the released code and the code used for the experiments in the paper?
In an era of widespread AI slop and fabricated papers, a reproducibility failure in officially released code is a serious ethical violation. Thank you.