The LMVD-ID is an internal research identifier, not an official CVE identifier.
RL-Based LLM Privacy Leak
Large Language Models (LLMs) are vulnerable to a novel agentic-based red-teaming attack, PrivAgent, which uses reinforcement learning to generate adversarial prompts. These prompts can extract sensitive information…
Paper-evaluated models
No paper-evaluated models are recorded for this entry.
Description
Large Language Models (LLMs) are vulnerable to a novel agentic-based red-teaming attack, PrivAgent, which uses reinforcement learning to generate adversarial prompts. These prompts can extract sensitive information, including system prompts and portions of training data, from target LLMs even with existing guardrail defenses. The attack leverages a custom reward function based on a normalized sliding-window word edit similarity metric to guide the learning process, enabling it to overcome the limitations of previous fuzzing and genetic approaches.
Examples
See repository at https://github.com/rucnyz/RedAgent (opens in a new tab). Specific examples of adversarial prompts generated by PrivAgent and their corresponding LLM outputs are provided in the paper's Appendix B and Appendix F.
Impact
Successful exploitation of this vulnerability can lead to the disclosure of sensitive information, including:
- System prompts: Compromising the intellectual property and functionality of LLM-integrated applications.
- Training data: Violating data privacy, intellectual property rights, and potentially revealing biases present in the training data.
Affected Systems
A wide range of LLMs, including both open-source (e.g., Llama 2, Mistral) and proprietary models (e.g., GPT-4, Claude), are potentially affected. LLM-integrated applications using vulnerable models are also at risk.
Mitigation Steps
- Improve the robustness of LLMs against adversarial prompt attacks through advanced training techniques, potentially including reinforcement learning with enhanced reward functions that specifically address the PrivAgent attack vector.
- Develop and deploy robust guardrail defenses that are capable of identifying and blocking a wider range of adversarial prompts, including those generated through reinforcement learning. These defenses should go beyond simple keyword matching.
- Implement input sanitization and validation mechanisms to filter or modify malicious inputs before they reach the LLM.
- Regularly update LLMs and their associated applications with security patches that address newly identified vulnerabilities.
- Employ advanced detection mechanisms such as anomaly detection to identify and flag unusual patterns in user input or LLM output, which could indicate a successful attack.
Research context and confidence
- Evidence and verification
- Paper-reported; independent reproduction is not documented.
- Primary research source linked.
- Severity
- Not rated by this catalog.
- Source and publication type
- arXiv · Research preprint.
- Peer-review status is not provided by this source.
- Author and publication status
- Author metadata is not stored; see the primary paper.
- Threat model and attacker access
- Black-box model, service, or application access.
- Related deployment categories
- Agent workflows
- Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
- Affected systems
- A wide range of LLMs, including both open-source (e.g., Llama 2, Mistral) and proprietary models (e.g., GPT-4, Claude), are potentially affected. LLM-integrated applications using vulnerable models are also at risk.
Research Paper
PrivAgent: Agentic-based Red-teaming for LLM Privacy Leakage
Primary source: arXiv. Findings are reported by the cited research and have not been independently verified.
View PaperEvidence
This entry is based on a primary research source. Its findings are paper-reported; independent reproduction and verification are not claimed.
https://arxiv.org/abs/2412.05734Related research
- Agent Lifecycle Compound Threats
Published March 1, 2026 · application-layer, infrastructure-layer, prompt-layer
- Arbitrary Agent Topology Breach
Published March 1, 2026 · application-layer, prompt-layer, injection
- Stage-Sequential Agent Escalation
Published March 1, 2026 · application-layer, prompt-layer, injection