Skip to content
#software testing Open access

AI Security Testing Outruns Its Evidence: A Literature Survey of the State of the Field as of October 2026

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research)
Software Testing and Debugging Techniques

Abstract

Artificial intelligence moved from an assistant for individual security-testing steps to a credible autonomous finder, exploiter and fixer of software vulnerabilities between 2023 and October 2026, but the evidence for that shift is uneven. This narrative survey synthesises research on four technical strands (AI-driven penetration testing and offensive automation; AI-assisted fuzzing and dynamic testing; AI-based vulnerability detection and automated repair, including the security of AI-generated code; and benchmarks and evaluation methodology) and two contextual strands (industry adoption and economics; risks, law and governance). Every claim is graded by evidence tier: peer-reviewed, preprint, government or organiser report, vendor claim, or secondary summary. The best organiser-scored result is the DARPA AI Cyber Challenge final (August 2025), in which seven cyber reasoning systems found 54 of 63 synthetic vulnerabilities and patched 43 at an average of about USD 152 per task. Peer-reviewed work supports a consistent design lesson: the reproducible gains come from hybrids in which a large language model supplies semantics (harnesses, specifications, taint sources, triage) and a deterministic component (fuzzer, static analyser, prover, exploit replay) supplies ground truth. By contrast, the most dramatic 2026 results, such as frontier models reported to find thousands of zero-day vulnerabilities, are vendor claims that third parties cannot yet reproduce. Independent benchmarks report far lower end-to-end autonomy than system papers, public benchmarks saturate or leak within 12 to 24 months, and about half or more of functionally correct AI-generated code remains exploitable in controlled studies. The binding constraints in 2026 are verification of findings, remediation capacity, safe operation of agents, and governance of access and disclosure, rather than discovery itself. We close with ten open problems and a statement of this survey's limitations.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

Microsoft Research Blog Oct 12, 2026

Simulating student learning for better AI tutoring

StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring appeared first on Microsoft Research.

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.