Google Strips OSS Bug Bounty Rewards From Its Rules

Google quietly removed OSS bug bounty reward amounts from its VRP rules, redirecting researchers on where to report, with an update due Q1 2027.

@sharedot

Google Strips OSS Bug Bounty Rewards From Its Rules

By @sharedot · · 6 pages

  • Programming
  • Open Source Security
  • Bug Bounty
  • AI

Google quietly removed OSS bug bounty reward amounts from its VRP rules, redirecting researchers on where to report, with an update due Q1 2027.

Reward amounts deleted from the rules

Google's pause of product vulnerability reports in its Open Source Software Vulnerability Reward Program came with a quieter edit: the published rules no longer list reward amounts for product vulnerabilities.

According to The Hacker News, the same change that added the notice of the stop removed the listed ranges — $500 to $7,500 for flagship projects and $101 to $3,133.7 for important ones — from Google's public GitHub copy of the rules on September 30, a day before the announcement on X. No date for reopening product vulnerability submissions was given; Google committed only to an update in the first quarter of 2027.

Reports filed before October 1 are still being processed.

Supply chain and cloud exceptions survive

The stop covers only product vulnerabilities — design or implementation flaws that substantially affect the confidentiality or integrity of user data in software built with the code.

Supply chain compromises, which could let someone tamper with a project's source code or published packages, keep their listed rewards of $3,133.7 to $31,337 for flagship projects, per The Hacker News.

The notice also names three routes for researchers: the Cloud VRP, which may still accept product vulnerability reports for some Google Cloud repositories at a cap of tier IT3b; the Patch Rewards Program, paying $100 to $15,000 for accepted patches; and Google's other reward programs, including the AI VRP.

The notice does not say whether Google will still take product vulnerability reports without a reward.

A year of escalating defenses against slop

The pause is the culmination of a slow squeeze. According to TechSpot, Google's human reviewers could no longer keep up with a surge of automated submissions, the vast majority invalid, and the company is "reformatting" the program in response.

The Hacker News reports that in March 2026 the program began requiring stronger proof for reports in some tiers — a patch merged into the project is one accepted form — with InfoWorld reporting at the time concern over AI-generated submissions containing invented trigger details.

In early September, the Go project added a section to its security policy on LLM-generated reports, warning that models are as good at reporting bugs that do not exist as finding real ones, and that reporters who forward large amounts of unfiltered LLM output will not be credited.

What it means for projects and hunters

The flagship tier — 26 repositories including Go, Angular, Flutter, Bazel and Protocol Buffers, alongside 47 important-tier projects — loses its fastest reward channel, and researchers must now route around it.

Angular's security policy, as of October 6, still points vulnerability reports to Google's Bug Hunters site with no alternative channel, while The Hacker News notes Go takes security reports by email to its own team and a GitHub organization policy points to g.co › vulnz.

TechSpot frames the episode as part of a wider strain, with Microsoft Edge, Linux and smaller FOSS projects facing the same flood — some smaller teams shutting the door on AI-generated contributions entirely.

Sources

  1. thehackernews.com › Google Pauses OSS Product Bug Bounty Rewards After Surge in Invalid Automated Reports
  2. techspot.com › Google pauses bug bounties for open source because AI slop reports are drowning its reviewers

More on Programming