Retrieval-augmented generation
RobustRAG
Superseded — cited as a baseline and beaten by newer methods
13 papers critique it · 8 beat it on benchmarks
What papers say
Verbatim critique sentences, each from a paper that cites RobustRAG as a baseline.
one cannot expect that LLMs always generate correct judgments, and thus the manipulated final input might lose crucial information or include wrong information before conducting answer generation
“Although existing defenses can mitigate the impact of poisoning attacks on RAG systems to some extent, they remain vulnerable to advanced attacks, where the attacker craft sophisticated strategies to bypass current safeguards”
“These approaches share an implicit assumption: if the system can identify poisoned evidence, it will naturally avoid acting on it. We show this assumption is incorrect. The deeper problem is the monitoring-control gap: models may detect contradictions and untrustworthy evidence, yet this awareness does not reliably govern their final output.”
“they suffer from additional computational overhead, such as multiple LLM inferences or substantial memory consumption.”
“For instance, RobustRAG~xiang2024certifiably fails when an attacker poisons more than half of the retrieved texts for a target question.”
“RobustRAG~xiang2024certifiably follows an "isolate-then-aggregate" pipeline, where answers are independently generated for each retrieved document and then aggregated. This approach not only incurs high inference costs but also becomes ineffective when the proportion of negative documents is high.”
“RobustRAG~xiang2024RobustRAG, as the major existing RAG framework for adversarial robustness, suffers from limited performance in benign (no-attack) scenarios and struggles in complex generation tasks.”
“For numerical manipulation: the poisoned passage is semantically identical to the original and will appear in top-k with high rank. The isolated response from the poisoned passage will say `$15,500` while responses from other passages (if any discuss the same topic) will say `$15,000.` However, in a mixed corpus with 1,000+ passages, the probability that multiple top-k passages discuss the exact same numerical claim is low. The poisoned passage often stands alone on its topic, making majority vote ineffective because there is no majority to outvote it.”
“the aforementioned defense methods necessitate the integration of additional large models, incurring considerable overheads. Meanwhile, it is difficult to promptly assess whether the current response of RAG is trustworthy or not. Moreover, they're all ``best-effort'' schemes, offering no guarantee on the defense effectiveness.”
“However, CAR~weller-etal-2024-defending and RobustRAG~xiang2024certifiably require multiple rounds of model inference, leading to inefficiency.”
“RobustRAG extracts document keywords as context, which also results in information loss.”
“Heuristic aggregation or filtering~xiang2024certifiably often causes utility loss, while optimization-based consistency selection~shenreliabilityrag typically relies on approximations without strong guarantees.”
Beaten on benchmarks
Head-to-head results where a newer method reports beating RobustRAG. Values are copied from the source paper's tables — verify against the cited paper.
RbFT beats RobustRAG
33.8 vs 10.1
EM · [Llama, Hard (τ=1.0) - Counterfactual]
RbFT: Robust Fine-tuning for Retrieval-Augmented Generation against Retrieval DefectsRA-RAG beats RobustRAG
0.552 vs 0.192
Accuracy (EM) · [NQ dataset, adversary-hammer prior]
Retrieval-Augmented Generation with Estimation of Source ReliabilityRAGShield beats RobustRAG
0.0 vs 88.0
Overall Attack Success Rate (%) · [Synthetic corpus, T3-H T6 T-TEMP Overall]
RAGShield: Provenance-Verified Defense-in-Depth Against Knowledge Base Poisoning in Government Retrieval-Augmented Generation SystemsGMTP beats RobustRAG
3.5 vs 54.0
ASR (Attack Success Rate) · [PoisonedRAG attack, Generation phase, NQ dataset]
Safeguarding RAG Pipelines with GMTP: A Gradient-based Masked Token Probability Method for Poisoned Document DetectionSampling + MIS beats RobustRAG
72 vs 51
RQA @Pos 50 · [Mistral-7B]
ReliabilityRAG: Effective and Provably Robust Defense for RAG-based Web-SearchRADAR beats RobustRAG
84.4 vs 60.4
Acc. · [Poison attack, k=50, Pos 1]
RADAR: Defending RAG Dynamically against Retrieval CorruptionMIS beats RobustRAG
72.1 vs 51.9
Bio @Pos 10 · [Llama3.2-3B]
ReliabilityRAG: Effective and Provably Robust Defense for RAG-based Web-Searchalg beats RobustRAG
0.99 vs 0.75
DACC · [NQ dataset / PRAGB attack]
Who Taught the Lie? Responsibility Attribution for Poisoned Knowledge in Retrieval-Augmented GenerationBRIDGE_GRPO beats RobustRAG
77.90 vs 62.50
Accuracy · [GPT-3.5-turbo / TRD Simu]
After Retrieval, Before Generation: Enhancing the Trustworthiness of Large Language Models in RAG
What to use instead
Recent methods in the same sub-problem, not yet superseded in the knowledge base — arXiv benchmark leaders, not vetted production recommendations.
- May 26, 2026
- May 19, 2026
- May 1, 2026
- Beyond Factual GroundingBeyond Factual Grounding: The Case for Opinion-Aware Retrieval-Augmented GenerationApr 13, 2026
- RAGShieldRAGShield: Provenance-Verified Defense-in-Depth Against Knowledge Base Poisoning in Government Retrieval-Augmented Generation SystemsApr 1, 2026
- Mar 24, 2026
- Jan 13, 2026
- Oct 10, 2025
- RADARRADAR: A Risk-Aware Dynamic Multi-Agent Framework for LLM Safety Evaluation via Role-Specialized CollaborationSep 28, 2025
- RAGOriginWho Taught the Lie? Responsibility Attribution for Poisoned Knowledge in Retrieval-Augmented GenerationSep 17, 2025