Google pauses new vulnerability reports as automated submissions burden review
Google pauses new vulnerability reports as automated submissions burden review
AI Cybersecurity

Google pauses new vulnerability reports as automated submissions burden review

IT ProOct 5, 2026

Google stopped accepting new product-vulnerability reports through its open-source rewards program, citing a rise in automated submissions that were mostly invalid.

Google has paused new product-vulnerability submissions to its Open Source Software Vulnerability Reward Program (OSS VRP), citing a significant rise in automated reports, most of which it said were invalid. The pause took effect on October 1, 2026, and the company said it would provide an update in the first quarter of 2027 as it revises this part of the program.

The change affects product-vulnerability reports submitted through the open-source program. Google said reports filed before the cutoff are not affected and indicated that some relevant reports may still be accepted through other channels, including its Cloud Vulnerability Reward Program. It also directed researchers to other reward programs or its Patch Rewards Program while the OSS VRP is being reworked.

The decision highlights a security-triage problem created by a sharp rise in low-quality automated submissions: generating reports can be inexpensive, but investigating and validating them still consumes human time. In the company’s statement, Google attributed the pause to the volume and low validity of submissions, rather than announcing a change to its process for handling already-filed reports.

For vulnerability researchers, the immediate practical effect is that this reporting route is unavailable for new product issues until Google changes or reopens it. Security teams and open-source maintainers may also need to account for shifting disclosure channels as organizations adjust their programs to handle automated reports. Google has not yet described the redesigned process, how it will distinguish useful reports from noise, or whether the pause will end after the next update.

The development is a notable operational response by a major technology company to AI-associated reporting pressure. It does not mean that all AI-assisted vulnerability research is invalid, nor that vulnerability reporting has stopped across Google’s other programs. The company’s Q1 2027 update should clarify whether it will introduce new submission controls, change eligibility rules or resume the affected intake process.

Industry Impact

Google redirects vulnerability reporting

Cybersecurity and open-source software

Overview

In the short term, researchers cannot submit new product-vulnerability reports through Google’s Open Source Software Vulnerability Reward Program; reports filed before October 1, 2026, remain unaffected. Researchers may need to use other Google programs or its Patch Rewards Program, where relevant. For security professionals and open-source maintainers, the pause underscores that automated reporting can increase triage workloads when submissions are mostly invalid. Google has not explained how it will redesign intake, and its first-quarter 2027 update will clarify whether controls, eligibility, or access change.

Key Impact Points

New product-vulnerability reports are temporarily blocked through this OSS VRP route.

Previously filed reports are unaffected, and some issues may still qualify through other channels.

Google’s response highlights the human validation burden created by high volumes of low-validity automated reports.

Opportunities

No clear commercial opportunity identified

Cybersecurity and open-source software

The article describes an operational challenge for vulnerability reward programs, but it does not identify a product, vendor, or market opportunity. Google has not yet outlined its redesigned process or said whether it will introduce new submission controls. While the need to distinguish useful reports from noise is clear, the article provides no evidence of demand for a specific commercial solution or of a viable revenue model. The immediate business relevance is therefore program management: researchers should verify available reporting routes, and organizations running similar programs can review how automated submissions affect their triage capacity.

Reference link

https://itpro.com/software/open-source/this-pause-is-due-to-a-significant-rise-in-automated-submissions-the-vast-majority-of-which-are-not-valid-google-pauses-open-source-bug-bounty-scheme-over-ai-slop-submissions

Image Source Link

https://www.abijita.com/wp-content/uploads/2026/10/Google-Pauses-Open-Source-Bug-Bounty-Program-Amid-Surge-in-AI-Generated-Reports.png

Community Discussion (0)

Loading discussions...