Google's Project Zero team conducted a detailed comparison of two automated tools used to hunt vulnerabilities in V8, the JavaScript and WebAssembly engine powering Chrome. The study pitted the generative JavaScript fuzzer Fuzzilli against BigSleep, an agentic system powered by large language models. Over a six-month period from April to September 2026, BigSleep discovered more vulnerabilities than Fuzzilli (45 versus 37), yet only roughly 25% of the bugs overlapped. Experiments on older bugs suggested the true intersection could reach approximately 60%.
Production Statistics
Both systems operate in production and report crashes through Clusterfuzz, which performs initial triage and creates bug reports in the Chromium tracker. Fuzzilli runs continuously across many instances and typically picks up new code changes within hours. BigSleep runs once per day, reviewing recent commits and generating proof-of-concept test cases for discovered issues.
Raw reports showed Fuzzilli producing 316 bugs and BigSleep producing 441. After filtering for vulnerabilities only and then for actionable reports (those not marked duplicate or WAI and linked to at least one fixing commit), the numbers became 37 for Fuzzilli and 45 for BigSleep. This represents a near tie with a slight edge for the LLM-based agent.
Overlap Analysis
Researchers measured overlap in two ways. First, they examined the bug tracker for reports filed by one system that were marked duplicates of reports from the other, including indirect duplicates resolved through Clusterfuzz signatures and fixing commits. For actionable vulnerabilities, the overlap reached approximately 25% (20 out of 81), with slightly more than half first discovered by Fuzzilli.
In a second experiment, BigSleep was tasked with rediscovering 112 historical Fuzzilli bugs from 2023 to mid-2026. The agent successfully reproduced the original bug in 62% of cases and found a different (already fixed) bug in another 12%. No statistically significant memorization effect was observed when comparing success rates across different time periods relative to the model's knowledge cutoff.
Bug Complexity and Components
Analysis of rediscovery rates by bug complexity (measured by time taken for Fuzzilli to find the issue) showed that harder-to-find bugs for the fuzzer were also harder for the LLM agent. Overlap was notably lower for bugs in compiler components, where Fuzzilli has specialized strengths.
The study concludes that both techniques remain valuable. A substantial portion of vulnerabilities was found exclusively by one method or the other. The rapid progress of LLM agents is encouraging, yet fuzzing and agentic analysis currently complement each other. The authors recommend that software projects apply both fuzzing and LLM-based analysis to reduce the number of vulnerabilities reaching end users.


