← Latest papers
💬 NLP

Exploring Cross-Client Memorization of Training Data in Large Language Models for Federated Learning

This paper proposes a novel framework to quantify both intra- and inter-client training data memorization in federated learning by adapting fine-grained cross-sample measurement techniques from centralized learning, revealing that FL models exhibit significant memorization risks influenced by specific training and inference factors.

Original authors: Tinnakit Udsa, Can Udomcharoenchaikit, Patomporn Payoungkhamdee, Sarana Nutanong, Norrathep Rattanavipanon

Published 2026-05-08
📖 5 min read🧠 Deep dive

Original authors: Tinnakit Udsa, Can Udomcharoenchaikit, Patomporn Payoungkhamdee, Sarana Nutanong, Norrathep Rattanavipanon

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a group of friends who want to learn how to cook a complex dish together, but they are too shy to share their secret family recipes. Instead of sending their actual recipes to a central kitchen, they each train their own version of the dish in their home kitchens and only send the lessons learned (the "weights" or adjustments) to a central chef. This is Federated Learning (FL). It's a way to learn collaboratively without ever sharing the raw ingredients (your private data).

However, there's a hidden danger: even if you don't share the recipe, the chef might accidentally memorize your specific ingredients and start spitting them out later when asked to cook something else. This is called memorization.

This paper is like a new "privacy detective" that investigates whether this accidental memorization is happening in Federated Learning, and how it differs from the old way of learning (where everyone did share their recipes in one big pot).

Here is the breakdown of their investigation using simple analogies:

1. The Old Detective vs. The New Detective

  • The Old Way (Centralized Learning): Previously, researchers checked if a model memorized data by asking, "If I give you this specific sentence (the prompt), will you spit out this exact sentence (the answer)?" They assumed the prompt and answer had to come from the same original recipe.
  • The New Problem (Federated Learning): In the "shy friends" scenario, a friend might ask the chef a question based on their recipe, and the chef might accidentally answer with a detail from another friend's secret recipe. The old detective missed this because they were only looking at one recipe at a time.
  • The New Framework: The authors built a new tool that checks cross-client memorization. They ask: "If Friend A gives a prompt, does the model accidentally reveal a secret from Friend B?"

2. The Investigation: What Did They Find?

The researchers set up a simulation with four different "cooking tasks" (Summarizing, Chatting, Answering Questions, and Classifying) and three "friends" (clients) with different datasets. They used a "plagiarism detector" (a tool that checks if text is copied, paraphrased, or just has the same idea) to see if the model was leaking secrets.

Key Finding A: The "Home" Bias
The model was much more likely to leak a friend's own secrets back to that same friend (Intra-client) than to leak Friend A's secrets to Friend B (Inter-client).

  • Analogy: If you ask the chef about your own family recipe, they might accidentally recite a detail from your own notes. But if you ask about your recipe, they are less likely to accidentally spill a secret from your neighbor's recipe. However, the neighbor's secret was still leaked, just less often.

Key Finding B: The "Short Prompt" Trap
They found that the length of the question (the "prefix") mattered a lot.

  • Analogy: If you give the chef a very short, vague prompt (like "Tell me about the soup"), the model is more likely to grab a random, memorized detail from the training data to fill in the blanks. If you give a long, detailed prompt, the model has more context to work with and relies less on memorized snippets.
  • Result: Shorter prompts = More memorization.

Key Finding C: The "Cooking Style" Matters
The way the model "decides" what word to say next (the decoding strategy) changed the results.

  • Analogy: Some cooking styles are more "creative" and risky. Using certain methods (like "top-p" or "top-k" decoding) made the model more likely to spit out memorized secrets, similar to how a chef who is trying to be too creative might accidentally use an ingredient from a neighbor's pantry.

Key Finding D: The "Recipe" Type Matters
They noticed that some types of tasks were safe, while others were risky.

  • The Safe Zone: In the "Classification" task (where the answer is just a single word like "Yes" or "No"), the model didn't memorize anything.
  • Why? The "plagiarism detector" needs a certain amount of text to work. If the model only generates one word, the detector can't find a match. It's like trying to catch a thief who only steals a single grain of rice; the security camera (detector) isn't sensitive enough to see it.

Key Finding E: The "Algorithm" Choice
They tested two different ways the friends could share their lessons (FedAvg vs. FedProx).

  • Result: One method (FedProx) caused the model to memorize more secrets than the other. It's like one group of friends sharing notes more aggressively, leading to more accidental leaks.

3. What They Didn't Find

  • Model Size: Making the chef smarter (using a bigger model) didn't clearly make them memorize more or less.
  • Practice Rounds: Having the friends practice more times (more communication rounds) didn't show a clear pattern of increasing or decreasing memorization.

The Bottom Line

The paper concludes that Federated Learning is not a magic shield against memorization. Even though the raw data isn't shared, the model still learns to "remember" specific details from the training data.

  • It remembers your own data more than others' data, but it does remember others' data too.
  • Short questions and certain "creative" settings make this leakage worse.
  • The way the friends share their lessons (the algorithm) changes how much is leaked.

The authors warn that we need to be careful: just because we aren't sharing the raw data doesn't mean the model isn't holding onto our secrets. They have released their "detective tool" (code) so others can check for these leaks in their own systems.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →