RAGLeak trains modified language-model generators to transform private retrieved context into reversibly obfuscated text that an attacker can decode from public-looking output. The study uses Qwen, Llama and Ministral families and synthetic experimental corpora representing healthcare, email and code. The backdoor is not an external command in the retrieved…
Inspect the ClaimsCase · DiggingBeagle record
Backdoored RAG model weights encode private retrieved documents into public answers
RAGLeak shows a controlled privacy extraction path through modified generator behavior rather than visible prompt injection alone.
Controlled model-poisoning experiments with three data domains, paper October 2026; no production data theft.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
Technical report or researcher-controlled experiments document the stated mechanism, but independent reproduction and population-wide prevalence are not established. Impact band is left unassigned because no calibrated damage threshold or representative victim impact is supported by the available record.
Assessed Oct 20, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-RAGLEAK-DATA · CLM-RAGLEAK-RATES · CLM-RAGLEAK-ENCODING · RAGLeak: supply-chain privacy backdoors in retrieval-augmented generation
At a glance
Retrieval authorization and response inspection need to account for unauthorized reconstruction of private content, not merely exact copied strings.
Read the implicationsNo affected commercial RAG deployment or independently confirmed private-user leak. The efficacy of access checks, response screening and clean fine-tuning outside the study is unknown.
Limits and uncertaintyFull account
RAGLeak trains modified language-model generators to transform private retrieved context into reversibly obfuscated text that an attacker can decode from public-looking output. The study uses Qwen, Llama and Ministral families and synthetic experimental corpora representing healthcare, email and code. The backdoor is not an external command in the retrieved document; it is a behavior carried by model weights combined with a later attacker query.
The authors report attack-success rates between 58% and 100% across selected settings. Tested similarity-based monitors reduced success by at most ten percentage points, but these are paper-specific defenses and configurations. No healthcare provider or enterprise customer is reported compromised. The operational failure requires a model with untrusted behavior plus private document access that lets the model release recoverable content to an unauthorized requester.
The adversary controls a generator component in the evaluated supply chain, while the defender provides private retrieval results. The encoded answer is the transport channel: it can conceal literal confidential strings from a naive output scan while retaining a reversible representation for the attacker. The synthetic datasets show feasibility under the tested checkpoint and prompts, not exposure of real patients, employees or commercial repositories.
Timeline
- Oct 19, 2026disclosure
Public disclosure
Claims & evidence
CLM-RAGLEAK-DATARAGLeak reports a backdoored model generator that can reversibly encode retrieved private information into its response in controlled datasets.supported
Basis: reported finding
- supportsRAGLeak: supply-chain privacy backdoors in retrieval-augmented generationprimary disclosure
Abstract; Attack overview; experimental domains
CLM-RAGLEAK-RATESAuthor-reported attack-success rates across experimental model and dataset settings span 58% to 100%, without documented production victims.supported
Basis: reported finding
- supportsRAGLeak: supply-chain privacy backdoors in retrieval-augmented generationprimary disclosure
Abstract; evaluation tables
CLM-RAGLEAK-ENCODINGThe controlled RAGLeak design uses a trigger-conditioned reversible transformation of retrieved data to lower literal leakage detection while preserving recoverability for the attacker.supported
Basis: reported finding
- supportsRAGLeak: supply-chain privacy backdoors in retrieval-augmented generationprimary disclosure
Paper Appendix E: reversible context obfuscation and alternative encoding schemes
Implications
Retrieval authorization and response inspection need to account for unauthorized reconstruction of private content, not merely exact copied strings.
Unknowns and contradictions
- No affected commercial RAG deployment or independently confirmed private-user leak.
- The efficacy of access checks, response screening and clean fine-tuning outside the study is unknown.
Sources and citation
Material revision history
- Oct 20, 2026 · Canonical change recorded · new in release · revision 177