Why AI does the search and a human makes the call
An AI-assisted code review finds suspicious spots in code quickly. Deciding which of them are real problems takes someone who understands the app and how people use it.
The makers of curl, a widely used open-source tool for network transfers, saw both sides of AI in security work within a single year. In May 2025, lead developer Daniel Stenberg wrote: “We still have not seen a single valid security report done with AI help.” People pasted code into a chatbot and forwarded the answer as a vulnerability, without checking whether it was true.
A few months later, the opposite happened. Security researcher Joshua Rogers sent lists of problems he had found with AI-assisted analysis tools. Together with a second researcher, he eventually reported over four hundred suspected issues. From the first list, the team merged about 50 bug fixes. The rest were partly false positives and partly minor issues the team did not think were worth fixing. Stenberg did not call the tools a revolution, but “an excellent new project assistant.”
The technology was the same. The difference was who used it. Stenberg later summed it up as “a clever person using a powerful tool.” The tool found the suspicious spots. Someone who understood the code decided what was real.
Research points the same way. When researchers had language models search for vulnerabilities in a strict test, even large models did not do much better than random guessing (Ding et al., 2024). Models are good at searching broadly and at connecting code across files. Whether a finding can really be exploited in your app is something a person has to check.
How does a security audit with AI work at Voltti?
An audit at Voltti has five steps. The models work mainly in step 2, the human in every step.