Google Pauses OSS Bug Bounty as AI Spam Floods Reports
By @sharedot · · 8 pages
- Programming
- Open Source
- Bug Bounty
- AI Spam
- Security
Google paused OSS VRP vulnerability submissions amid a flood of invalid AI-generated reports, promising a restructured program in Q1 2027.
What happened: Google freezes OSS VRP submissions
Google has paused product vulnerability submissions for its Open Source Software Vulnerability Reward Program (OSS VRP), announcing the freeze in a post on X. Per the company's own post, the pause took effect immediately on October 1 and applies specifically to product vulnerability reports, with Google citing "a significant rise in automated submissions, the vast majority of which are not valid."
The Times of India reports that AI-generated reports had overwhelmed security engineers and repository maintainers, forcing the operational freeze.
What stays open despite the pause
The shutdown is not total, and Google carved out several exceptions to keep critical disclosure channels alive.
According to the Times of India, valid product vulnerability filings logged before October 1 are unaffected, supply chain disclosures submitted under the OSS VRP remain open, and Google Cloud repository reports that directly impact Cloud products may still be accepted through the separate Google Cloud VRP.
Google is also directing security researchers toward its other active reward initiatives, including the Patch Rewards Program.
A pattern, not a one-off: Linux and Intel
The freeze fits a broader pattern that will resonate with working programmers.
Previously, Linux maintainers reported being completely flooded by bogus CVE filings after automated AI hunters drove recorded vulnerabilities to a record high of 2,000 per release, an influx so severe it forced the Linux project to drop support for older network drivers.
Chipmaker Intel also recently froze its bug bounty program, which offered payouts reaching $100,000 per flaw; the Times of India notes Intel did not cite synthetic submissions as the official cause, but industry analysts widely attribute the shutdown to identical AI spam bottlenecks.
Why it is surprising: bounty systems buckling under slop
A bug bounty pausing because it is too popular inverts the usual narrative, where reward programs are strained by too few quality reports, not too many bogus ones.
It's FOSS separately reports that open source maintainers are already "drowning in AI slop pull requests and bug reports" — a claim grounded in its coverage of the Node.js project's battles — and Google's experience shows the problem now extends from pull requests into vulnerability disclosure pipelines.
The economic engine of security research is effectively being clogged by automated noise at scale.
The stakes for open source security
It's FOSS's reporting on DigitalOcean quietly sunsetting its Open Source Credits program underscores the parallel squeeze — infrastructure support is shrinking for smaller projects at the same moment AI-generated noise raises their workload.
If fewer maintainers can afford to keep projects running, the disclosure channels depend on weaker upstream foundations.
What comes next: Q1 2027 update
Google says it will use the downtime to restructure the submission framework and has committed to giving an official progress update in Q1 2027, per the Times of India.
That gives the program roughly five months to design filters against automated submissions without discouraging legitimate researchers — a balance Intel and the Linux project have so far failed to strike.
Until then, researchers are told to route high-impact findings into Google's other VRP programs or the Patch Rewards Program, and the community will be watching whether the reformat actually holds the line against AI-generated noise.