AI · 4 Oct 2026 · 22:31 CEST
Jax’s PickGoogle froze its open source bug bounty program due to a ‘significant rise’ in AI submissions

What happened
Google’s official rules confirm that new product-vulnerability submissions to its Open Source Software Vulnerability Rewards Program have been paused since Oct 1, 2026. Earlier submissions and supply-chain reports remain covered. Google promises an update in the first quarter of 2027, without committing to a reopening date. TechCrunch attributes the pause to rising automated submissions.
Why it matters
The business lesson is to include verification in the workflow. A flood of plausible findings can create work for the receiving team. This is an operational interpretation, not evidence that every AI-assisted report is invalid or that all Google bounty programs have closed.
What to do next
Before an AI-generated security finding reaches an engineer or vendor, require the affected version, reproducible steps and evidence of impact. Have a person validate it. Track confirmed findings and review time alongside the number of reports.
ADDITIONAL STORY CONTEXT
Further context
Blaming a “significant rise” in AI submissions, Google has paused its open source bug bounty program until next year.
Last year, TechCrunch reported that cybersecurity experts were warning of that AI slop posed a serious risk to bug bounty programs. Looks like that’s the issue confronting Google’s Open Source Software Vulnerability Rewards Program, where researchers were rewarded for finding vulnerabilities in the company’s open source software.
In posts on X and the program website, Google
Source
TechCrunch AI · 4 Oct 2026 · 22:31 CEST
Open the original at TechCrunch AI ↗