Google Introduces $250,000 Root-in-Cloud Bug Bounty Reward

Hi, what are you looking for?

The top payout is for high-impact architectural research demonstrating full administrative control.

By

Flipboard

Reddit

Whatsapp

Whatsapp

Email

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 theroot-in-cloud validation criteriato 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.Advertisement. Scroll to continue reading.“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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 theroot-in-cloud validation criteriato 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.Advertisement. Scroll to continue reading.“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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 theroot-in-cloud validation criteriato 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.Advertisement. Scroll to continue reading.“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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 theroot-in-cloud validation criteriato 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.Advertisement. Scroll to continue reading.“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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 theroot-in-cloud validation criteriato 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.Advertisement. Scroll to continue reading.“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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated:Will AI Kill the Bug Bounty Industry?

The company has added theroot-in-cloud validation criteriato 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.Advertisement. Scroll to continue reading.“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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated: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 CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated:Will AI Kill the Bug Bounty Industry?

Related:Google Partially Reverses Chrome Bug Bounty CutsRelated:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated:Will AI Kill the Bug Bounty Industry?

Related:Google Narrows Open Source Bug Bounty Amid Wave of Invalid Automated ReportsRelated:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated:Will AI Kill the Bug Bounty Industry?

Related:Microsoft Bug Bounty Program: $20 Million Paid to 500 ResearchersRelated:Will AI Kill the Bug Bounty Industry?

Related:Will AI Kill the Bug Bounty Industry?

Ionut Arghire is an international correspondent for SecurityWeek.

Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights.

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

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.

Join as we bring together CISOs, senior cybersecurity executives, practitioners, industry experts, and other security leaders to share practical experience and examine the issues shaping enterprise cybersecurity strategy.

Barracuda has appointed Dan Fletcher as CFO.

Artemis Security has appointed Arun Singh as CGO.

General Paul M. Nakasone has joined Armadin’s Board of Directors.

As organizations eliminate passwords, attackers will adapt. Instead of attacking the authenticator directly, they will look for opportunities around it.(Torsten George)

Risk managers are trained to spot weak signals, plan for disruption and make hard decisions under uncertainty. But the discipline looks different when the risk is not a system or an enterprise, but you.(Steve Durbin)

The process that gates nearly every B2B deal is a self-assessment the sender distrusts and the receiver accepts. There is finally a better basis for trust between companies.(Sravish Sridhar)

Keep your patch management pipelines primed in case another round of Citrix NetScaler patches get released soon.(Tod Beardsley)

Where your developers sit on the AI adoption scale has a real impact on how you are addressing security risk.(Matias Madou)

Flipboard

Reddit

Whatsapp

Whatsapp

Email

Got a confidential news tip? We want to hear from you.

Reach a large audience of enterprise cybersecurity professionals

Subscribe to the SecurityWeek Daily Briefing and get the latest content delivered to your inbox.

Copyright © 2026 SecurityWeek ®, a Wired Business Media Publication. All Rights Reserved.