HAVE AI NEWS HAVE AI NEWS
tg subscribe
Tools

AI Guarding Open Source: Why Only a Fraction of Thousands of Discovered Bugs Get Fixed

AI Guarding Open Source: Why Only a Fraction of Thousands of Discovered Bugs Get Fixed

An analysis of Anthropic's security funnel: why the headline-grabbing claim of 29,000 discovered bugs and only 516 open-source patches distorts reality, and where the real bottleneck of automated auditing actually lies.

The primary bottleneck in open-source software security has become not the ability to detect a defect, but the time of human maintainers capable of verifying the bug and releasing a fix. Statistics from Anthropic's initiative clearly demonstrate this barrier: the advent of advanced language models like Claude Mythos allows generating thousands of bug reports, yet maintainer bandwidth remains a severe constraint.

What Anthropic's Security Funnel Revealed

A catchy headline circulated across tech media: a neural network uncovered nearly 30,000 vulnerabilities, but only 516 were fixed. Such a comparison creates a false impression of extremely low efficiency (around 1.8%). However, the actual vulnerability disclosure funnel works differently: 516 patches correspond to 6,157 reports actually submitted to open-source maintainers. The real fix rate for reported bugs is 8.4%.

According to Anthropic's coordinated vulnerability disclosure dashboard accumulated over six months of operation, the process is divided into two key stages.

Stage 1: Filtering Initial Findings

Models generate a colossal volume of hypotheses, but only a small portion reaches human reviewers:

Verification StageCountShare of Total
Candidates from neural networks29,439100%
Reviewed by six external security firms6,12320.8%
Confirmed by auditors as real bugs5,67492.7% of reviewed
Remaining in queue for analysis23,31679.2%

Stage 2: Maintainer Response

Even a confirmed vulnerability does not mean an update automatically appears upstream:

Interaction StatusCountExplanation
Sent to developers6,157Covers 591 projects
— with independent auditor report1,33321.6% of submitted
— direct feed without manual triage4,82478.4% of submitted
Response received from project team5,10382.9% response rate
Fixed upstream5168.4% of submitted
Registered security identifiers584Total of 219 CVEs and 365 GHSAs

How the OSS Scanner Service Works

Based on accumulated experience, Anthropic launched the OSS Scanner tool, modeled after Google's well-known OSS-Fuzz project. The service targets open-source repositories critical to infrastructure, and submissions are accepted via pull requests to the anthropics/oss-scanner repository.

Key features of the scanner:

  • Complete isolation: code is analyzed inside virtual machines with no network access.
  • Automated report generation: human involvement on Anthropic's side is eliminated. The model itself constructs a reproducible scenario, attempts to find the offending commit using git bisect, and drafts a proposed patch.
  • No rigid ultimatums: project authors are not currently subjected to the standard 90-day forced public disclosure deadline.

Why Fixes Are Far Fewer Than Findings

The gap between discovered issues and closed tickets is driven by the nature of open-source software maintenance, not merely the performance quality of neural networks:

  • Time factor: the cycle of preparing, testing, and releasing an update takes months. A bug accepted for work in early autumn simply cannot result in a release by the time the statistics are tallied.
  • Threat model conflicts: about 93% of the bugs reviewed by external firms are technically valid, but some are marked as "won't fix" by maintainers. A bug may reside in unreachable code or fall outside the scenarios that the project considers hazardous.
  • Severity overestimation: third-party auditors and project authors frequently downgrade the severity level assigned by the model. This discrepancy occurs because AI does not always accurately grasp the architectural context of a specific library.
  • Integration overhead: a drafted patch still requires regression testing and backporting to supported branches, imposing an additional burden on maintainers.

Despite the modest final fix rate, representatives of major projects like PostgreSQL, OpenSSL, and curl note that the quality of autonomous AI reports has improved dramatically compared to earlier generative experiments in previous years. Now, they genuinely help eliminate critical defects before malicious actors discover them.

Author: syntxaiofficial20 минут назад

Source: habr.com