Anthropic's CVD Dashboard Shows the Scale—and Bottlenecks—of AI-Assisted Vulnerability Discovery
Anthropic's August 26 coordinated-vulnerability-disclosure snapshot reports 2,300 disclosed findings across 392 open-source projects, highlighting both the reach of AI-assisted security research and the human triage/remediation bottleneck.
Anthropic turns AI-assisted vulnerability research into a measurable disclosure pipeline
Anthropic updated its coordinated vulnerability disclosure dashboard on August 26, 2026, publishing a new aggregate snapshot of security findings discovered with Claude models, independently triaged in many cases, and reported to open-source maintainers. The dashboard is useful less as a leaderboard than as a view into what happens when model-driven code analysis begins operating at substantial scale.
Anthropic says it began using an early snapshot of Claude Mythos Preview for open-source vulnerability research in February 2026 and later included findings from other Mythos-class and Claude models. Candidate findings are not treated as confirmed vulnerabilities automatically: Anthropic describes a process in which external security research firms or Anthropic staff reproduce, assess and prepare reports before high- or critical-severity issues are disclosed to maintainers, with some maintainers separately requesting direct untriaged reports.
The headline numbers
As of the August 26 snapshot, Anthropic reports 2,300 disclosed vulnerabilities across 392 open-source projects. It says 421 have been patched upstream to its knowledge, while 462 advisory identifiers have been issued across the ledger: 177 CVEs and 285 GitHub Security Advisories. A single finding can carry both kinds of identifier, so these figures should not be added to infer a unique-vulnerability count.
The dashboard also exposes an important scaling constraint. Anthropic shows a large funnel of model-generated candidate findings, but says independent human triage and review are the rate-limiting steps. That distinction matters: the practical value of AI-assisted security research depends not only on discovery volume but on confirmation quality, maintainer communication, patch production and eventual deployment.
Human review remains central
Anthropic reports a high true-positive rate among findings reviewed by external security firms, but it explicitly warns that this metric is only one proxy for impact. Real bugs can be duplicates, outside a maintainer's threat model or otherwise unlikely to be fixed. Upstream patches are a stronger lagging indicator, while even a released patch does not guarantee broad downstream installation.
That framing is important for security teams evaluating agentic or autonomous vulnerability-discovery systems. A model can generate a large number of plausible issues faster than maintainers and security researchers can responsibly validate them. Without triage capacity, coordinated disclosure processes can become the bottleneck rather than model inference.
A disclosure ledger designed for accountability
The dashboard uses a hash-commitment ledger for findings still inside their disclosure windows. Anthropic says a SHA-3-512 commitment is published once a finding has been validated, allowing the existence and commitment date of a sealed report to be demonstrated without exposing vulnerability details before coordinated disclosure has completed. More information is revealed as the finding progresses, while public technical details appear only after the disclosure window closes.
This approach is a notable governance pattern for AI-enabled security research: it creates a time-stamped public record without prematurely publishing exploitable details. The same principle could be useful wherever AI systems discover sensitive defects faster than the responsible-disclosure ecosystem can absorb them.
What the numbers do—and do not—prove
The dashboard does not establish that AI can replace human security researchers, nor that every model-generated finding translates into a meaningful real-world risk reduction. Instead, it provides evidence that frontier models can contribute materially to vulnerability discovery when paired with reproduction, external validation, maintainer coordination and disclosure controls.
For software maintainers, the operational challenge is increasingly downstream of discovery: prioritizing incoming reports, validating exploitability in project context, creating fixes, issuing advisories and helping users update. For AI labs, scaling responsible security research therefore requires investment in triage and remediation partnerships—not just stronger models or larger scanning budgets.
The August 26 snapshot is best read as a systems lesson: AI can expand the front end of vulnerability discovery dramatically, but security outcomes remain constrained by human validation, disclosure discipline and the capacity to patch software safely.
This article is built from the source material below. Open the originals for full context and the latest updates.