Threat Research Center Insights Vulnerabilities Vulnerabilities The Frontier AI Vulnerability Burst: Industrializing Autonomous Zero-Day Discovery in Open-Source Software 11 min read Related Products Unit 42 AI Security Assessment Unit 42 Frontier AI Defense Unit 42 Incident Response By: Xu Zou Published: August 4, 2026 Categories: General Insights Vulnerabilities Tags: AI Frontier AI Vulnerability Exploitation Zero-day Share Executive Summary Frontier AI is fundamentally shifting the dynamics of cybersecurity — accelerating both how vulnerabilities are discovered and how quickly they can be exploited. Our vulnerability research team built an autonomous vulnerability discovery, validation and reporting system that we call Network and Open-Source Vulnerability Analyzer (NOVA), an agentic research system that leverages proprietary AI harnesses powered by multiple leading frontier AI models. Our goal with this research is twofold: (1) contribute to improving the security of the software supply chain; and (2) ensure our customers are protected from vulnerabilities in the AI era. In just two months, NOVA analyzed 3,915 open-source software (OSS) projects and uncovered 14,090 confirmed vulnerabilities, 99.4% of which were previously unreported and 40% of them designated as high or critical severity. Nearly every frontier and open-weight model evaluated could find real vulnerabilities, with the strongest results coming from an ensemble of models, specialized security tools, and automated harnesses working together. These initial results illustrate just how dramatic the impact of AI is on the vulnerability landscape. In response to these significant results, we are actively partnering with open-source maintainers and clearinghouses such as Lightwell and Akrites to responsibly disclose these vulnerabilities and ensure they are patched upstream quickly and securely. Securing the broader open-source supply chain ultimately protects the entire software ecosystem and benefits everyone. Our experience with NOVA highlights a clear structural change: the patch window has collapsed. When vulnerability discovery accelerates, the time between disclosure and potential exploitation shrinks dramatically. And attackers need not have access to the latest frontier AI model to reverse engineer patches and develop exploits automatically. This new reality also makes virtual patching an even more important defense strategy in the AI era, and is a key driving force behind our recently announced Advanced Virtual Patching , the next evolution in network vulnerability protection. Advanced Virtual Patching is designed to operate at the speed of AI to keep pace with the new normal of higher rates of vulnerability discovery and compressed attack windows. By harnessing frontier AI to discover unknown vulnerabilities, and deploying protections in hours, we are collapsing the exposure window from the industry-average 55 days it takes to deploy a traditional patch down into a near-zero window of exposure. Our new “vaulted protection” technology enables us to deliver protections ahead of patch availability in a safe and responsible manner. In addition to these protections available with our network security platform, we recommend that organizations deploy relevant best practices, including vulnerability management, zero-trust network architecture, software supply chain security, and other attack surface reduction best practices. NOVA: Fully Automated Novel Vulnerability Discovery and Validation Our vulnerability research team built a fully autonomous vulnerability discovery system requiring no human in the loop until final review. We call this the Network and Open-Source Vulnerability Analyzer (NOVA). For each project we analyzed, NOVA performed the following functions: Review of the project history Reading the source code Identification of vulnerability candidates Creation of a working proof of concept (PoC) Deterministic validation of whether the vulnerability is triggered in a clean environment Generation of a patch candidate Production of a disclosure report The pipeline has scanned 3,915 projects across six major software ecosystems. It produced findings in every ecosystem we tested, for a total of 14,090 novel vulnerabilities. That scale changes how defenders should think about vulnerability discovery. Large-scale open-source vulnerability automation is not new: OSS-Fuzz launched in 2016 and, by August 2023, had helped identify and fix more than 10,000 vulnerabilities across 1,000 projects. It shows the step-change frontier AI enables: Work that once accumulated across years of specialized automation can now begin to happen across thousands of targets in a single autonomous campaign. Table 1 shows that the findings are distributed across very different software ecosystems: The PHP, Java/JVM and C/C++ rows include many larger web platforms, enterprise servers and system software projects, which produced dense clusters of findings per project The Go and JavaScript/TypeScript rows include broad package-ecosystem scans, where each individual package often produced fewer findings but could still affect many downstream products In other words, both large applications and small dependencies matter, but for different reasons. One matters because of direct exposed attack surface and the other because of supply-chain reach. Language or ecosystem Projects Findings Go 1,636 3,281 JavaScript/TypeScript 2,197 2,836 PHP 17 2,740 C/C++ 39 1,925 Java/JVM 14 1,784 Ruby/Python/Lua/Perl/Other 12 1,524 Total 3,915 14,090 Table 1. Autonomous pipeline findings by language or ecosystem. The projects we analyzed also varied widely in size. Figure 1 shows that most projects we studied were under 10,000 lines of code, but the scan also included larger applications and services. That matters because AI-driven vulnerability discovery is not limited to small demonstrations. The pipeline operated across projects ranging from small packages with hundreds of lines of code to large codebases with more than 1 million lines. Figure 1. The size distribution chart shows the share of scanned projects by lines of code. We then checked all 14,090 findings against the public record. Only 85 matched vulnerabilities already present in public sources, most published 2–8 weeks after our discovery. This small overlap suggests that many organizations are now independently scanning open-source software. It is reasonable to assume threat actors are doing the same. As AI-assisted discovery becomes easier to run, maintainers will face a growing volume of vulnerability reports that vary widely in quality, urgency and exploitability. What Kinds of Vulnerabilities AI Found Automation to find vulnerabilities is not a new concept. What we see from the NOVA research, however, goes much deeper than previous automations. Previous Impact of Automated Vulnerability Research Considering memory corruption helps shed light on how frontier AI changes vulnerability research. Memory corruption is one of the areas where vulnerability research was already highly automated before generative AI. Researchers have spent years using fuzzers to prove that machines can find crash-oriented bugs at scale. This is especially true in relation to memory corruption, null dereferences and integer overflows. While our system found many vulnerabilities in this category, it was not simply covering the same ground as previous automations. The type of vulnerabilities found with previous automations represent only a small fraction of the vulnerabilities found by NOVA. In the taxonomy we used for our frontier AI findings, the closest category, memory and calculation issues represented 557 findings or only 4.0% of the total. Even if resource-management and denial-of-service issues are added, these fuzzing-friendly categories total 1,121 findings — still only 8.0%. The Other 92% The vast majority of the analysis we did using frontier AI models — 92% — uncovered vulnerabilities of different types. When we look at the remainder we see that the AI harness was especially effective at identifying semantic and logic flaws such as: Access control and authorization Path traversal Code injection Prototype pollution Server-side request forgery (SSRF) Patterns of Vulnerabilities by Ecosystem We found that different ecosystems presented different types of risks. We broke down vulnerability types in relation to the ecosystems studied in Figure 2. (The figure reports percentages within each language, not raw finding volume, so it should be read as a vulnerability fingerprint for each ecosystem.) The clearest pattern is that the vulnerability mix follows how software is commonly built: C and C++'s issues are dominated by memory-safety and resource-management flaws, the cost of manual memory management JavaScript and TypeScript's issues concentrate in code injection, prototype pollution and SSRF, a byproduct of dynamic, package-heavy code Go's issues skew toward path traversal and SSRF, reflecting its common role in file-serving and proxy services PHP, Java and Python's issues are dominated by access-control and authorization flaws, the classic weak point of applications juggling many user roles Figure 2. Vulnerability type by language shows that each ecosystem has a distinct weakness profile. Severity of the Vulnerabilities Found A significant number of the 14,005 new vulnerabilities we found are considered severe. The Common Vulnerability Scoring System (CVSS), is a standard way to estimate vulnerability severity. Under CVSS 3.1, 4,030 findings (28.6%) scored High or Critical. Under CVSS 4.0, 5,600 findings (39.7%) scored High or Critical. Figure 3 shows the CVSS 4.0 distribution. Far from producing a long tail of low-impact issues, NOVA identified a substantial amount of vulnerabilities with the potential for real-world impact. Figure 3. CVSS 4.0 score distribution shows the share of findings by severity range. Supply-Chain Reach A vulnerability i