1. The problem is known, and the method is simple.
- Vision-language models refusing a request as text but answering it as an image is already known; the paper itself cites prior work on it (Section 1).
- SOT is a small LoRA-style adapter added to each MoE layer, trained so the image input's first answer token matches the text input's (Eqs. 2, 7).
2. The diagnosis does not show a cause beyond "text and image use different experts."
- Route transplantation only measures safety. Forcing the image input onto the text input's experts (Figure 3) is judged only by the safety margin. There is no check of general performance, so a forced route may simply break the model's computation. The test does not rule routing out.
- The gradient overlap restates routing. Experts that an input is not routed to get no gradient. So lower overlap between text and image (0.47 vs. 0.78; Figure 4a) is expected from different routing. It is not evidence that training causes the gap.
- Real safety training is ignored. The analysis assumes safety is learned from text and then transferred to images, using one hypothetical text-only gradient step (Table 1). Modern VLMs are also safety-trained on images, and the paper does not discuss how the base models were aligned.
- The claim that MoE makes the gap worse rests on one model pair. The only dense-vs-MoE comparison is Qwen3-VL-32B vs. Qwen3-VL-30B-A3B (1.9% vs. 10.7% text-safe, image-unsafe; Figure 1). These two models may differ in more than MoE, so one pair cannot show that MoE is the cause. More dense-vs-MoE pairs would be needed.
3. The natural baseline is missing.
- All baselines train the same added adapter as SOT, on only the first 4 tokens of the safe answer (Appendix B.3). None is standard LoRA fine-tuning of the model's own layers on image inputs with full safe answers.
- Even against these baselines, SOT clearly wins only on DeepSeek. On Qwen3, MM-PT is higher (89.8 vs. 88.9); on Aria, SOT and MM-SFT are within seed noise (63.2 vs. 62.6) (Table 2).
4. The utility claim is overstated.
- MMBench barely changes for any method (Table 14), so it cannot show that SOT preserves utility better than the baselines.
- On DeepSeek, SOT refuses harmless requests more than any other method (MOSSBench 1.3 to 18.3; XSTest-safe 8.0 to 17.6; Table 14).
5. The text-vs-image pairs are unclear for most benchmarks.
In HarmBench and BeaverTails-V, the harmful request is already in the text and the image only adds context. The paper does not say how the text-only versions of these benchmarks and SafeBench were built (Appendix B.2), so it is unclear that each pair is the same request in two forms.
Overall assessment The paper studies a real problem on released models and public benchmarks, and parts of the evaluation are careful: three seeds, Repair and Regression, a held-out out-of-distribution set, and a validated judge. The gain on DeepSeek is clear.
My main concern is that these do not support the paper's central claims. The text-safe, image-unsafe gap is already known. The diagnosis does not separate Safety-Write Fragmentation from the effect of different routing, and its evidence for shared parameters is a single reverted gradient step. The method is a small adapter with standard losses, and its advantage is clear on one of three models against baselines that share its adapter and short supervision window, at the cost of the highest over-refusal on that model. What would change my assessment is a diagnosis that controls for routing (Question 1) and a comparison with standard LoRA fine-tuning on the model's own layers with full safe responses (Question 3).