Google has stopped taking product-vulnerability reports in its Open Source Software Vulnerability Reward Program. The suspension started on October 1, 2026, the day the company announced it. Reports filed before that date still count. Supply-chain reports under the same program still count. Some Google Cloud repositories can still be reported through the Cloud program.

Tom's Hardware's account of the X post says the reason is invalid AI-written submissions. The program pays independent researchers who find defects in Google's public code: logic flaws, design bugs, broken code. That work used to be slow. Models and automated hunters cut the cost of filing a report, and maintainers then spent their time throwing out hallucinations instead of fixing the bugs that were real. Google said the maintainers were drowning in reports that named bugs and then failed the check. Thousands of them, in the account Tom's Hardware gives, were invalid or could not be exploited. The time went into reading the report. The patch queue waited. That is the mechanism behind an October 1 stop, not a claim that public Google code has run out of defects.

Linux hit 2,000 findings in a release

Earlier this month Linux maintainers said they were completely overwhelmed by CVE reports after AI hunters pushed the kernel to a record 2,000 vulnerabilities in a single release. Linux has also dropped support for some older network drivers because of false AI reports. Intel suspended a bounty that paid up to $100,000 a flaw. Intel has not said the cause was AI reports. Specialists quoted by Tom's Hardware suspect that it was.

The security tools that still work well are gated to a few vendors' machines. A bounty is the other door: anyone can file, and Google pays if the bug is real. When the filings stop being real, the door closes. Gabe Newell's old rule, that the defenders have to be right every time, is the workload those maintainers just described.

The Cloud program is still open

Google left two paths. Supply-chain issues in the open-source program are unchanged. Cloud product bugs can still go to the Cloud bounty, for some repositories that affect Cloud products. What ended on October 1 is the product-vulnerability lane of the open-source program, the one aimed at defects in public repos.

Intel's suspended bounty had paid up to $100,000 for a single flaw. The company has not given AI reports as the official reason. The suspicion in the piece is an inference by specialists, and it should stay labeled as theirs. Google's reason is on the record: invalid AI submissions. Linux's reason is also on the record, a flood of findings that included false reports, plus a record 2,000 vulnerabilities tagged in one kernel release. Three programs, three different degrees of certainty, one shared symptom. The people who used to get paid to read a careful report are reading a pile instead.

Google's remaining doors are narrower than the one that closed. Supply-chain reports in the open-source program continue. Cloud vulnerabilities can still be filed, and only for some repositories that affect Cloud products. A defect in a public Google repo that is neither a supply-chain issue nor a Cloud product no longer has this bounty. Linux maintainers used the phrase "completely overwhelmed." Intel's pause is the least documented of the three: a bounty that had reached $100,000 a flaw, and no official sentence blaming models. Google's sentence is the clear one, and it has a start date of October 1, 2026. The next sentence it has scheduled is an update in the first quarter of 2027, after it rebuilds the lane it just closed.