Case · DiggingBeagle record

Before-and-after weights can expose data an unlearning procedure was meant to erase

The TRACE paper reconstructs selected removed training examples from paired model checkpoints following approximate unlearning. The setting requires both checkpoints and does not establish exposure through final-model-only APIs.

Scope

Reconstruction rates depend on the benchmark, method and which checkpoints can be obtained. The paper does not show a universal extraction rate for all unlearning algorithms or production model deployments.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
demonstrated
Evidence
Grade B
Remediation
not applicable
AI role
AGAINST AI
Basis and provenance

Enrich update: CLM-ENRICH-20261027-34 cites SRC-2026-CP21-TRACE-UNLEARNING-DIFFERENTIAL at Abstract, before-and-after checkpoint access and reconstruction steps. New evidence concerns the bounded reported mechanism, prerequisite or outcome; setting evaluation; exploit status demonstrated; remediation status not_applicable. No independently comparable impact scale, affected production population or universal exploit success measure was established, so the impact band remains null. Original Claims remain individually attributable and any observed incident or simulated result is distinguished in the narrative.

Assessed Oct 27, 2026 using diggingbeagle.assessment/1.

At a glance

Timeline

  1. Oct 22, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-ENRICH-20261027-34TRACE assumes the attacker can obtain model snapshots from both before and after approximate unlearning, then uses embedding differences and a perplexity-gap search to reconstruct removed samples without possessing the original training examples.supported

Basis: reported finding

Link to claim
CLM-CP21-TRACE-UNLEARNING-DIFFERENTIAL-1TRACE demonstrates reconstruction against selected approximate-unlearning methods using paired pre-removal and post-removal checkpoints, with benchmark examples rather than a reported victim data leak.supported

Basis: reported finding

Link to claim

Implications

A model can pass ordinary final-model forgetting tests yet leak through version differences distributed to researchers or customers.

Controls and mitigations

  • Treat release of paired checkpoints as a separate privacy decision. Evaluate deletion claims against the actual attacker access model and independent prefix-reconstruction probes.

Unknowns and contradictions

  • Reconstruction rates depend on the benchmark, method and which checkpoints can be obtained. The paper does not show a universal extraction rate for all unlearning algorithms or production model deployments.

Sources and citation

Material revision history

  1. Oct 27, 2026 · Canonical change recorded · new in release · revision 196