REVIEW 2 cited by
Extracting Training Data from Document-Based VQA Models
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
Vision-Language Models (VLMs) have made remarkable progress in document-based Visual Question Answering (i.e., responding to queries about the contents of an input document provided as an image). In this work, we show these models can memorize responses for training samples and regurgitate them even when the relevant visual information has been removed. This includes Personal Identifiable Information (PII) repeated once in the training set, indicating these models could divulge memorised sensitive information and therefore pose a privacy risk. We quantitatively measure the extractability of information in controlled experiments and differentiate between cases where it arises from generalization capabilities or from memorization. We further investigate the factors that influence memorization across multiple state-of-the-art models and propose an effective heuristic countermeasure that empirically prevents the extractability of PII.
Forward citations
Cited by 2 Pith papers
-
A Lightweight Method to Disrupt Memorized Sequences in LLM
A decoding-time intervention that substitutes a small model's probabilities for common function words into a large model's output reduces exact training-data recall by up to 10x with minimal measured quality loss.
-
Beyond Visual Evidence: Revealing and Mitigating Relational Privacy Leakage in Document MLLMs
A dynamic relational unlearning framework and benchmark show that document MLLMs jointly leak correlated private fields under weak visual evidence, and that the framework lowers the leakage rate while partly preservin...
Discussion (0). Continue with ORCID to comment.