- Rating
- 3
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
The paper FedCURE is a framework for preserving LLM safety during federated fine-tuning when all clients and their training data are benign. The method identifies update directions that align with an erosion reference and are shared across clients, then filters their contribution to the global update. it also uses reference adapters for local stabilization and global safety restoration. The experiments show substantial safety improvements while generally retaining useful downstream performance.
Critical strengths
I find the focus on safety erosion under fully benign participation worthwhile. The paper goes beyond observing that safety deteriorates, it connects shared, erosion-aligned update components to the aggregated model. The energy-matched interventions in Figure 2 provide useful behavioral evidence that these components matter, rather than merely reflecting the magnitude of the removed updates.
I also appreciate the breadth of the evaluation. The results cover several model families and tasks, with additional experiments on multiple seeds, longer training, different client counts and data distributions, and alternative reference data, and the measurements are particularly helpful. All this make the safety gains of the complete framework convincing and support my positive assessment.
Critical weaknesses
My main concerns the is the comparison with the closest approach. Jailbreak to Protect (Ham et al., 2026), which the paper cites, already combines temporary jailbreaking during fine-tuning with a reinforcing adapter merged afterward, yet a federated adaptation is absent from the experiments. Since ERA and RRA account for substantial gains, I would like a direct comparison to better establish what FedCURE adds beyond bringing this approach into federated training.
I am also not fully convinced that the ablations isolate the benefit of consensus. In Appendix G.2, the variant without consensus introduces an additional cosine-similarity threshold of 0.5, changing the candidate pool as well as the selection rule. In Table 8, adding ECF to ERA–RRA on Dolly reduces harmful score from 2.44 to 2.03 but lowers ROUGE-L from 39.77 to 38.62. The Commonsense results are more favorable, so I view this as a need to clarify when consensus helps, rather than evidence that it is ineffective.
Questions for authors
Could the authors compare FedCURE with a faithful federated adaptation of Ham et al.’s Buffer-and-Reinforce framework using matched reference data and comparable training budgets? This would help me assess the contribution relative to the closest prior approach.
Does ECF retain its advantage when the consensus and no-consensus variants use exactly the same ERA-positive candidate pool? I would find multi-seed safety–task trade-offs for these variants helpful in judging the additional benefit of consensus.
3 comments
Response to Reviewer 4uqo (2/2)
Q2&W2: Isolating the Benefit of Consensus
We thank the reviewer for this question, which lets us clarify the benefit of consensus. We agree that the cosine threshold in our original no-consensus variant changes the candidate pool as well as the selection rule. We therefore repeat the comparison with the pool held fixed.
- Results are presented in Appendices G.4 and G.6.
1. Consensus vs. No-Consensus on the Same ERA-positive Pool
Both variants start from exactly the same ERA-positive candidate pool and differ only in what they remove: No-consensus removes the entire pool (no additional threshold), while Consensus (ECF) removes only the components shared across clients. The original cosine-thresholded variant (similarity to ERA ≥0.5) is kept for reference. Client-side ERA conditioning and RRA correction are off; ERA remains the server reference on Dolly, Dirichlet , 32 fully participating clients over three seeds.
| Variant | Pool | Consensus | HS↓ | Task↑ | Utility↑ | ΔOverall↑ |
|---|---|---|---|---|---|---|
| FedIT | – | – | 39.73±6.98 | 39.23±0.24 | 62.98±1.52 | -- |
| Cosine | thresholded | No | 29.30±20.13 | 38.52±0.93 | 64.38±2.88 | +11.11±18.08 |
| No-consensus | same | No | 2.88±0.08 | 25.32±0.12 | 65.41±0.17 | +25.36±8.58 |
| Consensus (ECF) | same | Yes | 5.68±2.44 | 35.96±1.07 | 70.20±0.95 | +38.00±6.91 |
On the same ERA-positive pool, the no-consensus variant suffers a large task score drop, severely degrading its safety–task trade-off. In contrast, with consensus, ECF achieves a competitive HS while largely preserving task performance and also improving utility, yielding the highest ΔOverall. This result is presented in Appendix G.6.
2. When ECF Helps
ECF is designed to help when clients’ marginal updates share erosion-aligned directions, using cross-client consensus to identify which ERA-positive components to remove. Even with ERA or ERA–RRA, we found that these components are not fully eliminated, leaving room for ECF to provide additional gains. As shown below, adding ECF reduces harmful scores and improves ΔOverall across all evaluated component pairings:
| Dataset | Component change | ΔHS↓ | ΔTask↑ | ΔUtility↑ | ΔOverall↑ |
|---|---|---|---|---|---|
| Dolly | ERA-only→ERA–ECF | −2.80 | +0.61 | +2.90 | +6.31 |
| RRA-only→ECF–RRA | −2.14 | +1.30 | +2.46 | +5.90 | |
| ERA–RRA→FedCURE | −0.87 | −0.56 | +2.18 | +2.49 | |
| Commonsense | ERA-only→ERA–ECF | −0.03 | −0.48 | +2.72 | +2.27 |
| RRA-only→ECF–RRA | −1.54 | −0.25 | +4.64 | +5.93 | |
| ERA–RRA→FedCURE | −1.80 | −0.43 | +2.98 | +4.35 |
To summarize, ECF complements ERA/RRA by filtering residual ERA-aligned components in each round’s aggregated marginal update. Its additional gains when combined with SafeLoRA, SaLoRA, and Multi-Krum further demonstrate its broader applicability, as shown in our response to Q1&W1. The conditions under which ECF provides additional gains are discussed in Appendix G.4, with supporting component comparisons in Table 14.
We appreciate your time and effort in reviewing our paper. We would be glad to answer any remaining concerns the reviewer might have.
Follow-up to Reviewer 4uqo
Dear Reviewer 4uqo,
Thank you again for your comments on our paper. With limited time remaining in the author-reviewer discussion period, we wanted to follow up and ask whether you have had a chance to check our response. We have added new results including (i) comparison with prior work (Ham et al., 2026) and (ii) clear ablations to isolate the benefit of consensus.
If you have any additional comments, we would be happy to address them before the discussion period ends.
Sincerely, Authors of Paper 55503
Response to Reviewer 4uqo (1/2)
Q1&W1: Comparison with Prior Work
We appreciate the comment on the comparison with Buffer-and-Reinforce (BnR) (Ham et al. 2026). We summarize our response as follows.
Below, we provide our detailed response.
0. Perspective Shift: from Local Intervention to Federated Consensus Filtering
Unlike BnR's model-level safety interventions in a centralized setting, FedCURE targets safety erosion caused by shared client updates accumulating across FL rounds. ECF leverages cross-client consensus to filter erosion-aligned updates at the server before they accumulate in the global adapter. Directly applying BnR to FL is not sufficient, as we describe below.
1. Algorithmic Differences from BnR
Like BnR, FedCURE uses reference adapters, but FedCURE introduces ECF, which applies consensus filtering to clients' marginal updates, and also trains and uses its adapters differently. BnR trains ReinforceLoRA with BufferLoRA active; FedCURE trains RRA independently on frozen W0: LRFedCURE(ϕR)=E(x,y)∼DR[−logpW0+ΔW(ϕR)(y∣x)]. In federated BnR, each client trains with BufferLoRA frozen and active; the equal-weight merge halves their trained LoRA updates ΔWU,i before factor averaging. FedCURE instead applies a convex merge by introducing c at the server to the ECF-filtered global adapter:
\Delta W_i^{\mathrm{BnR}}&=\mathcal{R}_r[\tfrac12(\Delta W_{U,i}+(I-\alpha P_{U,i})W_R^{\mathrm{BnR}})],\\\\ \Delta W_t^{\mathrm{FedCURE}}&=\mathcal{R}_r[(1-c)\Delta W_t^{\mathrm{stab}}+c(I-\alpha_b P_{T,t})W_R]. \end{aligned}$$ --- ## 2. Applying BnR to Federated Learning Both use the same reference data, training budget, and setup (Llama-3-8B-Instruct; deltas relative to FedIT). |Dataset|Method|HS↓|Task↑|Utility↑|ΔOverall↑| |---|---|---|---|---|---| |Dolly|FedIT|48.67|39.83|58.93|--| ||BnR|0.53|31.81|69.80|+50.99| ||**FedCURE**|2.03|38.62|68.21|**+54.71**| |Commonsense|FedIT|25.10|85.39|49.27|--| ||BnR|0.45|69.48|68.82|+28.29| ||**FedCURE**|1.58|84.36|67.54|**+40.76**| BnR not only loses task performance but also over-refuses on benign prompts, whereas **FedCURE keeps both HS and O-R low while preserving task performance, achieving a higher ΔOverall.** |O-R↓|FedIT|BnR|**FedCURE**| |---|---|---|---| |Dolly|2.80|13.60|**4.40**| |Commonsense|10.40|13.20|**5.60**| --- ## 3. ECF's Gain is Consistent Across Diverse Settings Beyond the differences between ERA/RRA and BnR, we further highlight the core novelty of FedCURE: Erosion Consensus Filtering (ECF). Even in extended federated fine-tuning over round 50, adding ECF to ERA/RRA components leads to consistent gains. ECF raises ΔOverall for every component pairing: |Dataset|Component change|ΔHS↓|ΔTask↑|ΔUtility↑|ΔOverall↑| |---|---|---|---|---|---| |Dolly|ERA-only→ERA–ECF|−2.80|+0.61|+2.90|+6.31| ||RRA-only→ECF–RRA|−2.14|+1.30|+2.46|+5.90| ||ERA–RRA→FedCURE|−0.87|−0.56|+2.18|+2.49| |Commonsense|ERA-only→ERA–ECF|−0.03|−0.48|+2.72|+2.27| ||RRA-only→ECF–RRA|−1.54|−0.25|+4.64|+5.93| ||ERA–RRA→FedCURE|−1.80|−0.43|+2.98|+4.35| --- ## 4. ECF is Plug-and-Play: Alone or on Top of Other Defenses Finally, we would like to highlight that ECF can be integrated with other safety tuning methods (e.g., SafeLoRA, SaLoRA) without requiring client-side ERA conditioning or RRA correction. ERA serves only as the server reference. When added to other defenses on Dolly, ECF lowers HS and raises ΔOverall against FedIT in all three cases: |Method|HS↓|Task↑|Utility↑|ΔOverall↑| |---|---|---|---|---| |SafeLoRA|45.67|39.63|60.31|+4.18| |**SafeLoRA+ECF**|11.83|38.17|65.67|**+41.93**| |SaLoRA|34.80|39.04|60.85|+15.00| |**SaLoRA+ECF**|26.87|38.67|62.32|**+24.03**| |Multi-Krum|44.89|39.19|60.29|+4.50| |**Multi-Krum+ECF**|6.83|37.99|67.61|**+48.68**| --- Overall, we believe that (i) the algorithmic differences between FedCURE and BnR, (ii) the novelty and effectiveness of ECF in FL, and (iii) ECF's compatibility with existing methods, collectively demonstrate the advantages of FedCURE. We hope these contributions provide insights into how to preserve LLM safety during federated fine-tuning with fully benign clients, a setting that has received limited attention.