Google to Auto-Publish Top Bug Bounty Reports

Google will start publishing some of its best bug bounty reports automatically. From 1 December 2026, any report sent to the Google and Alphabet vulnerability rewards programme that earns a payout of 10,000 dollars or more will be disclosed in public on Google's bughunters website, once the flaw has been fixed and enough time has passed since the fix and the payout.
The change was announced on 19 November on Google's security blog. It applies to the Google and Alphabet programme, known as the VRP, which pays outside researchers who find and responsibly report security flaws in Google's products. Google says the move is the first in a series of changes to the programme, with more tools and updates to follow.
Why Google is opening up its reports
The reason, Google says, is the way artificial intelligence has changed bug hunting over the past two years. Researchers are now using AI-assisted workflows to find flaws and to write up their findings, and the volume of reports has grown sharply. Google says it now sees fifteen times as many duplicate reports as it did in 2023, and the average report is three times as long as it used to be, because AI agents are being used both to discover vulnerabilities and to write the reports.
That flood of material is part of the problem the new policy is meant to solve. By publishing the strongest reports, Google wants researchers, and the AI agents they use, to learn from real examples of flaws that were found, confirmed and fixed. As the company put it, the change will create insights that assist researchers and agents, and ultimately help keep users safe.
Google already publishes vulnerability reports in two of its programmes. The Chrome VRP and the ChromeOS VRP both release all reported security flaws publicly once an appropriate amount of time has passed, and the wider Google and Alphabet programme has long allowed coordinated disclosure, in which a researcher publishes details after giving Google time to fix the problem. The new rule makes publication automatic for the biggest rewards instead of leaving it to each researcher to decide.
What gets published, and when
Four conditions must all be met before a report appears in public. It must have been submitted on or after 1 December 2026, and it must have been rewarded with 10,000 dollars or more by the Google and Alphabet VRP. At least 30 days must have passed since the report was fixed, and at least seven days since the reward was issued and the researcher was told about it. Reports tied to a special event or grant that may feature unreleased products and features are excluded.
The waiting periods matter. Nothing is published while a flaw is still open, and the gap after the fix gives Google time to make sure the repair has reached users before the details are shared. The published reports will appear on the bughunters site, where Google says the first automatically disclosed reports should start arriving in early 2027.
Google has also built in protections for the researchers themselves. Many do not want their name linked in public to a large cash amount, so they will be able to disclose anonymously. Researchers will also be able to suggest edits to their report before it is published, on top of Google's own privacy-preserving edits, so they can remove identifiers, cookies and other potentially sensitive content.
What comes next
Google says the disclosure change is only the start. It plans to keep updating the programme's rules, release more tooling, and add features including mirroring reports to GitHub, all aimed at helping both human researchers and AI agents. It also hopes other bug bounty programmes in the industry will follow its example and publish their rewarded reports too, so that the whole field can learn from the same pool of real findings.
The timing is notable. Google's Project Zero team has separately been shortening its own disclosure deadlines, arguing that AI has sped up both the discovery of flaws and the speed at which attackers can turn a patch into a working exploit. The VRP change pulls in the same direction: more of the detail about real flaws, shared sooner, in the open, once the fix is in place.