Build1 publisher2 min readPublished
Anthropic's red team finds open-source bugs faster than maintainers can ship fixes
Anthropic's Frontier Red Team has disclosed 6,157 open-source vulnerabilities and knows of upstream patches for 516. The gap sits with maintainers, whose capacity Anthropic's own policy treats as the ceiling on how fast it files reports.
The Engineer · Build desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

What happened
- Maintainers have acknowledged 5,103 of the disclosed reports, according to the dashboard's 2 October 2026 counts.
- The programme logged 29,439 raw findings between 1 November 2025 and 2 October 2026, and 6,123 of them went to human triage.
- Anthropic's disclosure policy sets a 7-day target for actively exploited bugs and waits 45 days after a patch before publishing technical detail.
- The programme began in February 2026 with an early snapshot of Claude Mythos Preview and uses external firms to reproduce and assess findings.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- decision Downstream teams that size their exposure from the disclosure count will plan around fixes that do not exist yet; the upstream release count is what they can deploy against.
- constraint Extra discovery capacity at Anthropic will lengthen the queue of confirmed but unsent findings, because disclosure volume is capped at what maintainers can absorb.
- exposure Each upstream patch starts a 45-day clock to public technical detail, so operators slow to install it end up running an unpatched system with a published writeup.
- contradiction The post places the 8.4% four months into the programme; by the dashboard's February 2026 start it is about eight, a slower pace than the post implies.
Divided out, 516 fixes against 6,157 disclosures is an 8.4% patch rate [17]. Acknowledgement runs at 82.9% [18]. At least 4,587 reports that a maintainer has seen still have no known upstream patch [19]. The Netics Labs write-up on dev.to, which summarises the dashboard, argues that automated discovery has moved the constraint downstream, with patch rate bounded by the capacity of the projects receiving the reports [15]. Those projects are largely run by volunteers or small teams, the post notes, and each triaged report still has to be understood, reproduced, fixed, tested and released [16].
I think that reading holds, and Anthropic's own policy is the evidence. The programme commits to pace submissions to what maintainers can absorb [7]. The disclosure count is throttled before it is ever published. Only about 20.8% of raw findings reached human triage at all [20]. The dashboard also concedes that some findings confirmed as real remain unsent "due to capacity limitations" inside the programme itself [13].
The About page tells readers which of its own numbers to discount. I would like more dashboards to ship with that page. It says the true-positive rate includes real bugs already reported elsewhere and real bugs a maintainer decided not to fix [11]. The patch count is "a more reliable one", it says, though "patches take a long time to create" [12]. Even that count stops at release. The dashboard says a released patch "does not guarantee that those patches have been widely installed" [14].
For 8.4% to measure maintainer speed, most disclosures would need to be old enough to have run past the 90-day deadline and its 14-day extension [7]. The post does not break disclosures down by age. The patch figure is also a floor. Anthropic counts only fixes it knows about [2], and maintainers sometimes ship a fix without publishing an advisory [9]. A team watching feeds sees 584 identifier records, 219 CVEs and 365 GitHub Security Advisories [9]. Those records equal about 9.5% of the disclosure count [21]. They cover fewer findings than that, because one finding can carry both identifiers [9].
One figure in the post does not reconcile. It says external firms reviewed 5,674 candidates and confirmed 92.7% of the 6,123 as true positives [22]. Applied to 6,123, that rate gives about 5,676 confirmations, two more than the firms reviewed [24]. Another 4,824 findings went straight to maintainers without the independent check, at the maintainers' own request [6].
The disclosure plumbing is careful work. Findings still inside their window appear only as commitment hashes, so their existence and date can be proved while the content stays withheld [8].
What to watch
- The next dashboard update, to see whether the patched count rises as early disclosures pass the 90-day deadline and 14-day extension.
- Whether Anthropic publishes disclosure ages or a time-to-patch distribution, so slow fixes can be separated from recent reports.
- Whether disclosure volume flattens as the pacing commitment meets a growing queue of confirmed findings.