AEGLIX News
Google has expanded its Cloud Vulnerability Reward Program with a new premier reward tier of $250,000 for Root-in-Cloud bugs, according to a program announcement. The top-tier reward targets vulnerabilities that grant full administrative control over arbitrary Google Cloud organizations, representing the highest bounty in the program's history.
The Root-in-Cloud category encompasses tenant-isolation bypasses and complex cross-service logic flaws that provide complete administrative control equivalent to the roles/owner permission or full IAM control over arbitrary Google Cloud organizations or projects. To qualify, researchers must demonstrate this level of access without any prior access to the victim project, compromised credentials, social engineering, or user interaction. The program also established that valid reports demonstrating remote code execution in Google's underlying production infrastructure, known as Borg, or achieving root-in-prod will automatically be evaluated by the Google Cloud VRP panel for Root-in-Cloud eligibility.
Google implemented a deterministic proof-of-root mechanism using a designated service account that allows researchers to cryptographically prove unauthorized access against that specific identity. The program includes strict rules of engagement: researchers who achieve execution on Google's production infrastructure must immediately stop probing, as escalating privileges, obtaining production credentials, or performing lateral movement are prohibited and will result in disqualification from the reward.
Since launching its first Vulnerability Reward Program in 2010, Google has rewarded thousands of security researchers worldwide with more than $81.6 million in total payouts. In 2025, the company awarded a record-breaking $17.1 million to over 700 security researchers, representing a 40% increase from 2024 when it awarded $12 million. Separately, Google suspended submissions to its Open Source Software Vulnerability Rewards Program in October following a flood of AI-generated reports.
Report prepared 2026-11-05 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)