Skip to content

Google Pauses OSS VRP Product Bug Bounty Rewards Over AI-Generated Submission Surge

Google Pauses OSS VRP Product Bug Bounty Rewards Over AI-Generated Submission Surge

Effective October 1, rewards for product vulnerabilities in Go, Angular, Flutter, and 70+ other open-source projects have been quietly removed — with no confirmed return date until at least Q1 2027.

Diagram showing Google OSS VRP scope: supply chain compromises and other security issues retain rewards; product vulnerabilities are paused as of October 1 2026 due to a surge in automated submissions, with a Q1 2027 update committed
Google OSS VRP scope after the October 1 pause. Product vulnerability rewards are suspended; supply chain and other security issue rewards remain. Source: Generated by UnpanicTech.

Google stopped accepting product vulnerability reports through its open-source bug bounty program on October 1, 2026. The change affects the Open Source Software Vulnerability Reward Program (OSS VRP) — the program that covers projects like Go, Angular, Flutter, Bazel, and Protocol Buffers — and was announced with minimal detail on the same day it took effect.

The reason given: a sharp increase in automated submissions, most of which Google says are not valid. No figures were provided. Google did not specify whether AI tools were the source of the problem, though the pattern closely matches concerns the program's team had already raised publicly earlier this year.

What the OSS VRP Is and What Just Changed

Google launched the OSS VRP in August 2022 [1] to pay researchers for finding security flaws in Google-maintained open-source software — a category that covers an enormous amount of widely-used infrastructure. Under the program, projects are ranked in four tiers based on sensitivity. The top two — flagship and important — are the ones that carried product vulnerability rewards.

Flagship repositories include Go, Angular, Flutter, Bazel, and Protocol Buffers. Google's tiered repository list, updated in mid-September, names 26 flagship and 47 important repositories. That's 73 projects where researchers could previously earn rewards for finding design or implementation flaws affecting user data confidentiality or integrity.

As of October 1, none of them pay rewards for product vulnerabilities [2]. The change was committed to Google's public GitHub copy of the rules on September 30 — a day before the X post — with the commit message "OSS VRP product vuln pause."

The Reward Table: What's In, What's Out

Category Flagship (26 repos) Important (47 repos) Standard
Supply chain compromises $3,133.7 – $31,337 ✓ $1,337 – $13,337 ✓ $500 – $3,133.7 ✓
Product vulnerabilities Paused (was $500–$7,500) Paused (was $101–$3,133.7) None
Other security issues $1,000 ✓ $500 ✓ None

Source: Google OSS VRP rules, GitHub commit f8bf23a, September 30 2026 [2]. The fourth tier (low-priority projects) has no listed rewards in any category.

Supply chain compromises — flaws that could allow someone to tamper with source code or published packages — keep their rewards across all tiers. So do other issues like leaked credentials that grant write access. Product vulnerabilities, the category most commonly associated with traditional security research, are the only thing suspended.

This Wasn't Entirely Sudden

The OSS VRP team had been struggling with submission quality for a while. In March 2026, Google tightened the rules to require stronger proof for reports in certain tiers — a merged patch being one accepted form of evidence [3]. At the time, reporting by InfoWorld indicated the team was particularly frustrated by AI-generated submissions that included invented technical details about how vulnerabilities could be triggered.

The Go project added language to its own security policy in early September addressing the same issue [4]. The wording is unusually direct for official policy documentation:

"Modern LLMs are very good at finding real and important security bugs. Unfortunately, they are also very good at finding imaginary issues, or real issues that are not security bugs."

The policy asks reporters not to forward unfiltered LLM output, and states plainly that those who do will not receive credit for real findings buried in the noise. That's a policy for managing the problem, not eliminating it — and apparently the problem grew worse before October anyway.

OSS VRP Timeline

Timeline of Google OSS VRP events: launched August 2022, stricter proof requirements March 2026, Go LLM report policy September 2026, product vulnerability rewards paused October 1 2026, update promised Q1 2027
OSS VRP timeline from launch through the current pause. Source: Generated by UnpanicTech.

The AI Submission Problem, Examined

It's worth being precise about what Google did and didn't say here. The X post from GoogleVRP cited "a significant rise in automated submissions, the vast majority of which are not valid." That's the extent of the official explanation. Google did not say the submissions were AI-generated, did not name any tools, and gave no numbers.

The connection to AI tools comes from context, not from the October 1 statement itself. Earlier in 2026, the OSS VRP team had expressed specific concern about low-quality AI-generated reports — many of which described vulnerabilities with fabricated trigger conditions. The Go project's September policy update made the phenomenon explicit. But whether the October surge was the same population of reporters, or a new wave of automation, isn't known.

What's analytically interesting here is the failure mode. The problem isn't just that AI tools write bad security reports. It's that they write plausible-looking bad reports — reports that require a human expert to evaluate and reject, even when the underlying finding is imaginary. The triage cost of processing a flood of those reports is real, and it falls entirely on the program's staff. Tightening proof requirements in March apparently wasn't enough.

Where Researchers Should Submit Reports Now

Decision flowchart for researchers who find a product vulnerability in Google open-source software: if it affects a Google Cloud repo, check the Cloud VRP; if not, consider the Patch Rewards Program if you can write a fix; otherwise use project-specific channels like security at golang dot org or g dot co slash vulnz
Where to route product vulnerability reports after the October 1 pause. No path currently guarantees a cash reward for product vulnerabilities in OSS VRP-covered projects. Source: Generated by UnpanicTech.

The OSS VRP rules name three alternative routes [5]:

  • Cloud VRP: For flaws in Google Cloud-maintained open-source repos that affect Cloud products, the Cloud VRP may still accept product vulnerability reports. The notice is qualified — it says "may" — and Google doesn't name which repositories qualify. Under Cloud VRP rules, open-source repo flaws affecting Cloud products are rated at most IT3b (the tier for lower-priority products and acquisitions) unless the product list says otherwise. Worth checking before submitting.
  • Patch Rewards Program: This one pays for fixes, not reports — and only after the project's maintainers accept the patch and it has been in place for a month. Rewards range from $100 to $15,000. A patch that fixes a single vulnerability is evaluated case by case. If you can develop a working fix, this path is still open.
  • Other Google reward programs: If a vulnerability in an OSS project also affects something covered by a separate program — Google's AI VRP, for example, or a product-specific program — submitting there is the recommended route.

Outside those three, individual projects have their own reporting channels. Go accepts vulnerability reports by email to security@golang.org [4] and has a 90-day remediation commitment. The broader Google security reporting address, g.co/vulnz, accepts reports for other projects. Angular's security policy, as of October 6, still points researchers to the Bug Hunters site — it hasn't been updated to reflect the pause or offer an alternative channel.

What none of these paths currently guarantee is a cash reward for a product vulnerability in an OSS VRP-covered project. Google's notice doesn't say whether it will continue taking reports without payment in the interim. That's one of the genuinely unanswered questions here.

What This Means for Researchers and Open-Source Security

The practical impact depends entirely on how long this lasts. Google committed to an update in Q1 2027 — that's the first quarter of next year, a window that could mean January or it could mean late March. No more specific date was given, and the notice doesn't say whether the program will resume in its previous form, in a modified form, or whether some categories of projects will return to reward-eligible status before others.

For researchers who focus on OSS VRP projects, the immediate effect is a gap in the incentive structure. Supply chain work — finding ways to compromise build pipelines, package signing, or source code integrity — still pays well and still matters. But a classic implementation bug in a widely-used library like Protocol Buffers or the Go standard library doesn't carry a financial incentive right now, regardless of its actual severity or impact.

That's worth thinking about from a structural standpoint. Bug bounty programs don't just pay researchers; they help prioritize what gets looked at. A program gap isn't likely to mean that major vulnerabilities go unreported — researchers with genuine findings will typically still report them, and some projects like Go have their own channels and crediting systems. But the volume and diversity of eyes on these codebases may drop during the pause, especially from researchers who split their time across multiple programs based on where the incentives are.

The harder question is what Google does with the program when it returns. The March 2026 rule changes were meant to filter out low-quality submissions without suspending rewards entirely. They clearly didn't work well enough. A Q1 2027 restructuring that doesn't solve the triage problem would just restart the same cycle.

What Remains Unknown

Several things aren't answered by the available information:

  • Whether the volume of invalid submissions was predominantly AI-generated, or involved other forms of automated scanning.
  • Whether Google will accept valid product vulnerability reports without a reward during the pause, or whether the program is effectively closed for that category.
  • Which specific Google Cloud repositories might still be eligible for product vulnerability reports through the Cloud VRP.
  • Whether the Q1 2027 update will restore the program in its previous form, restructure it significantly, or cap rewards at lower levels to reduce the financial incentive for bulk automated submissions.

Google has not elaborated beyond the X post and the GitHub commit. If the situation changes, the OSS VRP rules page is the place to check.


Sources & References

  1. Google Launches New Open-Source Bug Bounty to Tackle Supply Chain Attacks — The Hacker News, August 2022
  2. OSS VRP product vuln pause — Google/bughunters commit f8bf23a, September 30 2026 (GitHub)
  3. Streamlining Google's OSS VRP: Key Rule Updates — Google Bug Hunters blog, March 2026
  4. Go Security Policy (including LLM-generated reports section) — go.dev
  5. Google Open Source Software Vulnerability Reward Program Rules — bughunters.google.com

Published: October 6, 2026. All sources verified at time of publication.

NK

Cybersecurity Researcher & Technical Editor

UnpanicTech publishes independent cybersecurity research and defensive security analysis. Naseem Khan serves as Technical Editor, with a focus on vulnerability analysis, defensive security, incident response, cloud security, and practical security engineering.

Leave a Comment (Authenticated Users)