Google has expanded its Cloud Vulnerability Reward Program (VRP) with a new $250,000 top-tier reward for security weaknesses that could lead to full administrative control. The premier payout is “specifically designed to recognize high-impact architectural research” and will be handed out to researchers who can demonstrate gaining ‘roles/owner’ privileges or complete IAM control over arbitrary Google Cloud organizations or projects. According to the internet giant, to qualify for the reward, the exploit path should not depend on pre-existing access to a project, previously compromised credentials, or user interaction/social engineering. Reports that demonstrate remote code execution (RCE) in Borg (Google’s underlying production infrastructure) or root-in-production will also be evaluated for the new $250,000 root-in-cloud reward . “Because code execution in Borg has the potential to impact service availability or cross-tenant data, researchers must halt all probing immediately upon achieving any execution in Borg. Escalation, extracting production credentials, and lateral movement are not allowed and will result in researcher disqualification,” Google Cloud CISO Chris Betz said. The company has added the root-in-cloud validation criteria to its Cloud VRP page, explaining that it will award the bug bounty if its analysis of the initial entry point, execution context, and attack surface demonstrates that full arbitrary tenant or project takeover is possible. “Identifying tenant-isolation bypasses and complex cross-service logic flaws requires human creativity, intuition, and rigorous systems analysis combined with the power of agentic systems,” Betz noted. According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
The premier payout is “specifically designed to recognize high-impact architectural research” and will be handed out to researchers who can demonstrate gaining ‘roles/owner’ privileges or complete IAM control over arbitrary Google Cloud organizations or projects. According to the internet giant, to qualify for the reward, the exploit path should not depend on pre-existing access to a project, previously compromised credentials, or user interaction/social engineering. Reports that demonstrate remote code execution (RCE) in Borg (Google’s underlying production infrastructure) or root-in-production will also be evaluated for the new $250,000 root-in-cloud reward . “Because code execution in Borg has the potential to impact service availability or cross-tenant data, researchers must halt all probing immediately upon achieving any execution in Borg. Escalation, extracting production credentials, and lateral movement are not allowed and will result in researcher disqualification,” Google Cloud CISO Chris Betz said. The company has added the root-in-cloud validation criteria to its Cloud VRP page, explaining that it will award the bug bounty if its analysis of the initial entry point, execution context, and attack surface demonstrates that full arbitrary tenant or project takeover is possible. “Identifying tenant-isolation bypasses and complex cross-service logic flaws requires human creativity, intuition, and rigorous systems analysis combined with the power of agentic systems,” Betz noted. According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
According to the internet giant, to qualify for the reward, the exploit path should not depend on pre-existing access to a project, previously compromised credentials, or user interaction/social engineering. Reports that demonstrate remote code execution (RCE) in Borg (Google’s underlying production infrastructure) or root-in-production will also be evaluated for the new $250,000 root-in-cloud reward . “Because code execution in Borg has the potential to impact service availability or cross-tenant data, researchers must halt all probing immediately upon achieving any execution in Borg. Escalation, extracting production credentials, and lateral movement are not allowed and will result in researcher disqualification,” Google Cloud CISO Chris Betz said. The company has added the root-in-cloud validation criteria to its Cloud VRP page, explaining that it will award the bug bounty if its analysis of the initial entry point, execution context, and attack surface demonstrates that full arbitrary tenant or project takeover is possible. “Identifying tenant-isolation bypasses and complex cross-service logic flaws requires human creativity, intuition, and rigorous systems analysis combined with the power of agentic systems,” Betz noted. According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
Reports that demonstrate remote code execution (RCE) in Borg (Google’s underlying production infrastructure) or root-in-production will also be evaluated for the new $250,000 root-in-cloud reward . “Because code execution in Borg has the potential to impact service availability or cross-tenant data, researchers must halt all probing immediately upon achieving any execution in Borg. Escalation, extracting production credentials, and lateral movement are not allowed and will result in researcher disqualification,” Google Cloud CISO Chris Betz said. The company has added the root-in-cloud validation criteria to its Cloud VRP page, explaining that it will award the bug bounty if its analysis of the initial entry point, execution context, and attack surface demonstrates that full arbitrary tenant or project takeover is possible. “Identifying tenant-isolation bypasses and complex cross-service logic flaws requires human creativity, intuition, and rigorous systems analysis combined with the power of agentic systems,” Betz noted. According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
“Because code execution in Borg has the potential to impact service availability or cross-tenant data, researchers must halt all probing immediately upon achieving any execution in Borg. Escalation, extracting production credentials, and lateral movement are not allowed and will result in researcher disqualification,” Google Cloud CISO Chris Betz said. The company has added the root-in-cloud validation criteria to its Cloud VRP page, explaining that it will award the bug bounty if its analysis of the initial entry point, execution context, and attack surface demonstrates that full arbitrary tenant or project takeover is possible. “Identifying tenant-isolation bypasses and complex cross-service logic flaws requires human creativity, intuition, and rigorous systems analysis combined with the power of agentic systems,” Betz noted. According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
The company has added the root-in-cloud validation criteria to its Cloud VRP page, explaining that it will award the bug bounty if its analysis of the initial entry point, execution context, and attack surface demonstrates that full arbitrary tenant or project takeover is possible. “Identifying tenant-isolation bypasses and complex cross-service logic flaws requires human creativity, intuition, and rigorous systems analysis combined with the power of agentic systems,” Betz noted. According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
“Identifying tenant-isolation bypasses and complex cross-service logic flaws requires human creativity, intuition, and rigorous systems analysis combined with the power of agentic systems,” Betz noted. According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
According to Michael Cote, Google Cloud’s vulnerability reward program lead, first-time researchers who combine their own intuition with agentic tools are finding more interesting bugs, on average, than novices did two years ago. He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
He also pointed out that finding bugs eligible for the new root-in-cloud tier requires deep architectural intuition and AI. “High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
“High incentives require clear, safe rules of engagement. We never want researchers testing exploits against real customer projects. Instead, we created a deterministic proof-of-root mechanism using a designated service account. Researchers can cryptographically prove unauthorized access against that identity,” Cote said. Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
Related: Google Partially Reverses Chrome Bug Bounty Cuts Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
Related: Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated Reports Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
Related: Microsoft Bug Bounty Program: $20 Million Paid to 500 Researchers Related: Will AI Kill the Bug Bounty Industry?
Related: Will AI Kill the Bug Bounty Industry?
Ionut Arghire is an international correspondent for SecurityWeek.
More from Ionut Arghire
Bulletproof Host Virtualine Loses Its Domain to FBI Seizure
Fresh WordPress Vulnerability in Attackers’ Crosshairs
Max-Severity GitLab Vulnerability Exploited Against Alpine Linux
TeamViewer Flaw Could Let Malicious Hosts Take Over Support Technicians’ Machines
Adobe, Veeam, Juniper Networks Patch Critical Vulnerabilities
Over 41,000 DHS Employee Records Leaked Online
HHS Filing Puts iRhythm Data Breach Toll at 8.2 Million
Chinese Hackers Quietly Used Low-Severity ESXi Logging Flaw as Zero-Day
Malicious Claude Code Extension Served in Cursor Supply Chain Attack
Chainalysis Discloses Data Breach Following AI-Driven Cyberattack
Polymarket Returns $3.9 Million to Traders as DebugBear Cites DNS Hijack
FBI Flags Over 600 Addresses Tied to North Korea’s Binance Heist
Ivanti Patches Two More Zero-Days Exploited in Connect Secure Attack Chain
Northstar Security Exits Stealth With $7M to Expose Toxic Risk Combinations
Syrian Hacker Gets Prison Time in US After Over a Decade on the Run
PHP2Shell Attacks Root Palo Alto Firewalls but Fail Against WordPress
Webinar: Agentic Pentesting for a Stronger CTEM Program
Close the security gaps between pentests. Join this session to explore agentic pentesting and gain a practical framework for continuous exposure validation in your CTEM program.
Virtual Event: CISO Forum 2026 Summit
Join as we bring together CISOs, senior cybersecurity executives, practitioners, industry experts, and other security leaders to practical experience and examine the issues shaping enterprise cybersecurity strategy.
Flipboard Whatsapp Whatsapp Email
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
