Crimson AI NewsA CrimsonLingua Network service
EN ع
← Back to news
Research paper Hugging Face

Split-LLM Training Leaks Real Data Through Zero-Gradient Patterns, Study Finds

AI By Crimson AI Hugging Face Papers 8 September 2026 · 00:00 16 views
Share: X Telegram

A systems-security case study shows that a split-LLM training setup passed its privacy checks while the returned gradient revealed which rows were real, enabling token-recovery attacks. Clipping and noising every gradient row closed the leak at a modest utility cost, but five attack classes remain unmeasured.

Split-LLM Training Leaks Real Data Through Zero-Gradient Patterns, Study Finds

Key points

A new systems-security case study examines a two-node split-LLM training architecture and finds that its privacy evaluation passed even though an observable channel remained untested. In this setup, a Trusted Local Node (TLN) sends protected activations to an Untrusted Cloud Node (UCN); the UCN returns its output, and the TLN, which holds the private loss, sends back the output gradient.

The frame the cloud node receives mixes real data rows with synthetic decoys, and the loss function ignores those decoys. Because the decoys contribute nothing to the loss, their gradients are exactly zero, and the resulting pattern of zeros reveals which rows were real. The researchers measured this with a protocol fixed in advance: a leak injected at known strength to confirm the instrument could detect one, a shuffled-label control to confirm it would not report absent leaks, and a threshold set before the runs.

Across nine seeds, the zero patterns identified the real rows on every frame — 4,096 of 4,096 per run. An attack on frame contents recovered roughly one extra token per hundred over a constant-guess baseline, an improvement of +0.65 to +1.50 percentage points, while the shuffled controls recovered nothing. A second set of runs repeated the result on a configuration that keeps model quality within budget, indicating the finding is not confined to an unrealistic deployment setting.

On both datasets, every such run passed the forward-channel privacy check and the quality check, yet failed that same privacy check once the returned gradient was included. Clipping and noising each row of the gradient closed the leak for about 0.01 nats of held-out cross-entropy.

The authors caution that the system is not thereby safe. Five classes of attack, including those that accumulate observations across training steps, were never measured. The study frames the underlying tension as a utility-privacy conflict: the security boundary is the network connection between the local and cloud nodes, and noise cannot be added indefinitely without harming the model's ability to learn.

MetricResult
Seeds tested9
Real rows identified per run4,096 of 4,096
Token recovery over constant-guess baseline+0.65 to +1.50 percentage points
Shuffled-label control recoveryNone
Utility cost of clipping and noising every gradient row~0.01 nats of held-out cross-entropy
Attack classes left unmeasured5
Source
Hugging Face · Hugging Face Papers
Related news
Research paper
Hugging Face 15 Oct 2026

New Survey Maps How Multimodal AI Agents Remember and Evolve

A Hugging Face survey proposes a two-axis framework for multimodal agent memory, separating how information is formed and represen...

7
Research paper
Hugging Face 15 Oct 2026

CriticOPD Fixes On-Policy Distillation by Letting Teachers Critique Student Errors

Hugging Face researchers introduce CriticOPD, a method that restores the teacher's ability to recover from student mistakes during...

8
Research paper
Hugging Face 15 Oct 2026

ActionOPD: Distilling Agent Decisions, Not Tokens

A new Hugging Face paper proposes ActionOPD, an action-level on-policy distillation method that aligns a student agent's decisions...

9