Skip to content

Back to the catalog

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

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

Google Cloud Vulnerability Reward Program has added a $250,000 root-in-cloud tier for exploits that give roles/owner or full IAM control over arbitrary Google Cloud organizations or projects. The exploit path cannot rely on prior project access, stolen credentials or social engineering. Remote code execution in Borg also qualifies, but researchers must stop probing immediately. Proof is made against a designated service account using a deterministic proof-of-root mechanism.

TL;DR Google adds a $250,000 Cloud VRP tier for full tenant or project takeover and Borg code execution, with a safe proof-of-root service account.
Document

What it is

Google Cloud's Vulnerability Reward Program has a new top tier of $250,000, called root-in-cloud. It pays for a demonstrated path to roles/owner or complete IAM control over arbitrary Google Cloud organizations or projects. Google Cloud CISO Chris Betz and VRP lead Michael Cote described it, and the criteria are now on the Cloud VRP page.

Preconditions / Affected

The exploit path must not depend on any of these:

  • existing access to a project
  • previously compromised credentials
  • user interaction or social engineering

Reports showing remote code execution in Borg, Google's production infrastructure, or root-in-production are also evaluated for this tier.

What to do

For researchers considering a submission, the page sets these rules:

  • Prove access cryptographically against a designated service account, using Google's deterministic proof-of-root mechanism. Do not test against real customer projects.
  • Stop all probing at the first execution in Borg. Escalation, extracting production credentials and lateral movement lead to disqualification.
  • Expect Google to judge the entry point, execution context and attack surface. The award goes out if that analysis shows full arbitrary tenant or project takeover is possible.

Caveats

The page gives no payout conditions for partial impact, no tiers below this one, and no details of the proof-of-root mechanism or the designated service account. Betz and Cote say the targeted bugs, such as tenant-isolation bypasses and cross-service logic flaws, need deep architectural insight combined with agentic tooling. That is their view, not a measured result.

Organisations named here

  • Chris Betz
  • Google
  • Michael Cote

Technologies named here

  • Google Cloud
  • Borg (Google's underlying production infrastructure)
  • Cloud Vulnerability Reward Program (Cloud VRP)
  • Deterministic proof-of-root mechanism

Techniques named here

  • Remote code execution
  • Cross-service logic flaws
  • Privilege escalation to roles/owner
  • Tenant isolation bypass

Concepts named here

  • Agentic tools in vulnerability research
  • Cloud VRP
  • Cross-tenant data impact
  • Root-in-cloud
  • Rules of engagement

Also named here

  • Borg