Google Pauses Open-Source Bug Bounty Program Due to AI-Generated Spam

Key Takeaways

• Google has temporarily suspended new product vulnerability submissions to its Open Source Software Vulnerability Reward Program (OSS VRP).
• This pause, effective October 1, 2026, is a direct response to a surge in AI-generated, invalid vulnerability reports.
• The program will continue to accept supply-chain vulnerability reports and honor product vulnerability submissions made before the cutoff date.
• Google expects to provide an update on the program’s future in the first quarter of 2027.

Google Halts Open-Source Bug Bounty Submissions Amid AI Spam Influx

Google has enacted a temporary suspension on new product vulnerability reports submitted to its Open Source Software Vulnerability Reward Program (OSS VRP). The decision, which took effect on October 1, 2026, comes after a significant increase in automated submissions, most of which proved to be invalid or unexploitable.

The tech giant anticipates providing further details on the program’s status in the first quarter of 2027. This move does not constitute a complete shutdown of the open-source bug bounty initiative; reports related to supply-chain vulnerabilities remain within scope, and Google will process all product vulnerability submissions received prior to the October 1 deadline.

The Challenge of AI-Generated Reports

Google stated that the pause was necessitated by a “significant rise” in automated vulnerability disclosures, with the vast majority failing proper validation. These AI-generated submissions often present as technically sound but may include fabricated exploit paths, erroneous assumptions about source code behavior, or claims of reachable vulnerable functions that are, in fact, inaccessible. Such inaccuracies place a substantial burden on security engineers and open-source project maintainers responsible for triage.

The company had previously cautioned researchers about this emerging issue in earlier updates to its OSS VRP rules. Google specifically noted instances of AI-generated reports containing incorrect triggering conditions and “hallucinations” regarding potential exploitation methods. In response, the program had already tightened evidence requirements for specific report types, particularly memory corruption flaws in high-priority projects.

Certain vulnerabilities found within Google Cloud repositories may still be eligible for submission through the distinct Google Cloud Vulnerability Reward Program.

Scope of the OSS VRP

Google’s OSS VRP encompasses the latest versions of open-source projects hosted in public repositories under Google’s ownership. This includes a broad spectrum of issues, such as flaws in code, repository configurations, GitHub Actions workflows, access controls, build systems, release environments, package publication credentials, and cryptographic signing keys.

The highest priority remains supply-chain compromises. Researchers can report vulnerabilities that could enable an attacker to alter source code, tamper with build artifacts, compromise packages distributed via registries, or misuse build and release infrastructure. Such submissions require demonstrating a realistic and exploitable attack path, moving beyond purely theoretical risks.

Rewards for supply-chain vulnerabilities in flagship OT0 projects range from $3,133.7 to $31,337. Important OT1 projects can yield between $1,337 and $13,337, while standard OT2 projects are eligible for $500 to $3,133.7. Google does not offer monetary rewards for low-priority OT3 repositories, and all reward amounts are subject to the company’s security impact assessment.

The specifically paused category covers product vulnerabilities. These include software weaknesses like memory corruption in parsers or network implementations, path traversal flaws, sanitizer failures, and insecure default configurations that could significantly compromise the confidentiality or integrity of user data in applications leveraging Google’s open-source code.

Google’s move highlights a growing challenge for vulnerability disclosure programs globally. While generative AI tools can assist researchers in code review, proof-of-concept development, and pattern identification, reports fundamentally require meticulous manual validation, reproducible steps, accurate impact analysis, precise affected version details, and a clear attack scenario.

Security researchers are advised against submitting AI-generated findings without thorough verification against a recent build. A high-quality report should include a buildable proof of concept, exact reproduction instructions, crash data where applicable, concrete evidence of reachability, and a clear explanation of the security implications.

Google is directing researchers toward its other VRP programs and its Patch Rewards Program while it redesigns the intake process for paused OSS product vulnerabilities.

What You Should Do

• For Researchers: Thoroughly validate all findings, especially those assisted by AI tools, before submission. Ensure reports include a reproducible proof of concept, detailed steps, and clear impact analysis.
• For Open-Source Maintainers: Remain vigilant regarding the quality of vulnerability reports. Implement robust triage processes to filter out invalid or AI-hallucinated submissions.
• For Organizations Utilizing Google Open Source: Stay informed about Google’s OSS VRP updates. Continue to monitor and patch vulnerabilities as they are disclosed through official channels.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.