Autonomous vulnerability discovery is finding the bug classes fuzzing cannot reach — Unit 42 reports 92% of its pipeline's open-source findings are logic and access-control flaws, not memory-safety bugs

Unit 42 has published results from NOVA, a fully autonomous multi-agent, multi-model vulnerability-discovery pipeline that runs scoping, discovery, proof-of-concept verification and gatekeeping stages in a sandboxed environment with no human review until final disclosure (Palo Alto Networks Unit 42, 2026-08-04). Over two months it analysed 3,915 open-source projects across six ecosystems and produced 14,090 confirmed vulnerabilities, 99.4% of which were previously unreported, with around 40% designated high or critical severity.

The composition of those findings is more consequential than the count. Unit 42 records that the vast majority of the analysis — 92% — uncovered vulnerabilities of different types than the memory-safety bugs that dominate automated discovery (Palo Alto Networks Unit 42, 2026-08-04): access control, path traversal, code injection, prototype pollution and server-side request forgery. That distinction is the operational point. Coverage-guided fuzzing finds crashes, and a crash is a proxy for memory corruption; it is not a proxy for "this endpoint does not check whether the caller is allowed to do this". A decade of assurance built around fuzzing harnesses and memory-safety scanners was structurally blind to the category this pipeline is best at, which means an OSS project's history of clean automated analysis says less about its semantic-flaw exposure than teams have assumed.

A second finding cuts against the idea that one model is the tool: Unit 42 states that every model contributed a large set of findings that no other model found (Palo Alto Networks Unit 42, 2026-08-04). Discovery capability here is additive across models rather than converging on a single best one — which, read from the offensive side, means the ceiling for an adversary running the same design is set by breadth of access rather than by picking the strongest model.

Unit 42 also reports 5,421 findings tied to 1,280 vulnerable dependencies, producing downstream exposures in consuming applications, a majority of which it validated as exploitable from the consuming application rather than only in the library. Unit 42 states it disclosed through maintainers and clearinghouses before publication.

These figures are Unit 42's own measurements of its own pipeline and have not been independently verified, so the direction of the finding is more reliable than the precision of any individual number.