> ## Content Index
> Fetch the complete content index at: https://blog.harshkohli.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Google Cloud Pays $250k for Root-in-Cloud Bugs
- URL: https://blog.harshkohli.com/google-cloud-vrp-250k-root-in-cloud/
- Published: 2026-11-03T13:04:12.000Z
- Updated: 2026-11-03T13:04:12.000Z
- Description: Google Cloud VRP adds a $250,000 Root-in-Cloud tier for full tenant takeover bugs with no prior access. Rules, proof-of-root, and what admins should do.
- Author: Harsh Kohli
- Tags: Tech News, Software

Google Cloud just put a quarter-million dollars on the table for one class of bug: proving you can take full admin control of someone else's Cloud org without ever logging into it. That is a serious bump for researchers who dig into tenant isolation, not another low-tier XSS payout.

## What happened

In a [Cloud CISO Perspectives post dated October 29](https://cloud.google.com/blog/products/identity-security/cloud-ciso-perspectives-introducing-new-tier-for-google-cloud-vrp?ref=blog.harshkohli.com), Google Cloud CISO Chris Betz and Cloud VRP lead Michael Cote introduced a new **$250,000** Root-in-Cloud reward (about ₹2.4 crore at \~₹95/$). [BleepingComputer covered the change today](https://www.bleepingcomputer.com/news/google/google-adds-new-250-000-cloud-vrp-reward-for-root-in-cloud-bugs/?ref=blog.harshkohli.com), and [@BleepinComputer flagged it on X](https://x.com/BleepinComputer/status/2117589200404914349?ref=blog.harshkohli.com).

To hit that tier you have to show full administrative control — the equivalent of `roles/owner` or complete IAM control — over arbitrary Google Cloud organizations or projects, with no prior access and no special project setup. Stolen credentials, phishing, and any user interaction are out. Valid RCE in Google's Borg production infrastructure, or root-in-prod findings, can also be reviewed for Root-in-Cloud eligibility.

Google is not inviting people to poke real customer projects. Researchers prove access cryptographically against a designated service account. If you land execution on Borg, you stop. Escalation, pulling production credentials, or lateral movement gets you disqualified. The updated rules and proof-of-root details sit on the [Cloud VRP rules page](https://bughunters.google.com/about/rules/google-friends/4849867320328192/cloud-vulnerability-reward-program-rules?ref=blog.harshkohli.com).

Betz's post also notes Google has paid more than $81.6 million through its broader VRP programs since 2010, with a record $17.1 million in 2025 alone. Separately, Google paused OSS VRP submissions in October after a flood of AI-generated reports — a different program from Cloud VRP, but it shows why Google wants fewer noisy tickets and more high-impact ones.

## Why it matters

Cloud breakouts are rare, ugly, and expensive when they work. Paying $250,000 for a clean tenant-isolation bug is Google saying those findings are worth more than the automated scanner noise filling most bounty inboxes. If you run workloads on GCP — or you rotate keys after a host breach the way I walked through for [Railway](https://blog.harshkohli.com/railway-breach-rotate-api-keys/) — this is the kind of research that keeps your neighbors' projects from becoming your problem.

## What to do

- If you research Google Cloud security, read the Root-in-Cloud rules and the proof-of-root mechanism before you test anything near Borg.
- If you are a GCP admin, treat this as a reminder to tighten IAM, watch for unexpected `setIamPolicy` changes, and keep org policies boring and strict.
- Do not treat a high bounty as a green light to probe someone else's production project. Google will not pay for that path, and you can get yourself banned.