Repairing vulnerabilities without invisible hands. A differentiated replication study on LLMs
Not on the map. Why?
Abstract (arXiv)
Background: Automated Vulnerability Repair (AVR) is a fast-growing branch of program repair. Recent studies show that large language models (LLMs) outperform traditional techniques, extending their success beyond code generation and fault detection. Hypothesis: These gains may be driven by hidden factors -- "invisible hands" such as training-data leakage or perfect fault localization -- that let an LLM reproduce human-authored fixes for the same code. Objective: We replicate prior AVR studies under controlled conditions by deliberately adding errors to the reported vulnerability location in the prompt. If LLMs merely regurgitate memorized fixes, both small and large localization errors should yield the same number of correct patches, because any offset should divert the model from the original fix. Method: Our pipeline repairs vulnerabilities from the Vul4J and VJTrans benchmarks after shifting the fault location by n lines from the ground truth. A first LLM generates a patch, a second LLM reviews it, and we validate the result with regression and proof-of-vulnerability tests. Finally, we manually audit a sample of patches and estimate the error rate with the Agresti-Coull-Wilson method.
Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). Builds on 18 of its 41 references that are in the map. First posted on arXiv 28 Jul 2025.
Builds on
18 of 41 references.
References · 18
- 2025DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via Reinforcement Learningcited by 6,330
- 2023Large Language Models for Software Engineering: A Systematic Literature Reviewcited by 399
- 2020Deep Learning based Vulnerability Detection: Are We There Yet?cited by 144
- 2024Vulnerability Detection with Code Language Models: How Far Are We?cited by 139
- 2021Examining Zero-Shot Vulnerability Repair with Large Language Modelscited by 105
- 2023How Effective Are Neural Networks for Fixing Security Vulnerabilitiescited by 52
- 2023ChatGPT for Vulnerability Detection, Classification, and Repair: How Far Are We?cited by 44
- 2024Large Language Model for Vulnerability Detection and Repair: Literature Review and the Road Aheadcited by 42
- 2024Top Score on the Wrong Exam: On Benchmarking in Machine Learning for Vulnerability Detectioncited by 28
- 2024A Case Study of LLM for Automated Vulnerability Repair: Assessing Impact of Reasoning and Patch Validation Feedbackcited by 22
- 2024Hybrid Automated Program Repair by Combining Large Language Models and Program Analysiscited by 22
- 2023AIBugHunter: A Practical Tool for Predicting, Classifying and Repairing Software Vulnerabilitiescited by 17
6 more
- 2024LLM Security Guard for Codecited by 15
- 2024Software Vulnerability and Functionality Assessment using LLMscited by 11
- 2024Toward Improved Deep Learning-based Vulnerability Detectioncited by 9
- 2024Instruct or Interact? Exploring and Eliciting LLMs' Capability in Code Snippet Adaptation Through Prompt Engineeringcited by 6
- 2025Combining Large Language Models with Static Analyzers for Code Review Generationcited by 6
- 2025Using ML filters to help automated vulnerability repairs: when it helps and when it doesn'tcited by 1
Built on by
Citing papers per year: 2025: 1.
1 paper.