- Top reward
- $250,000
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $250,000
- top reward.
- Report as the policy says
- The policy page explains how.
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Top reward
-
$250,000
The $250,000 "Root-in-Cloud" reward is for demonstrating full administrative takeover ( roles/owner equivalence) of arbitrary Google Cloud organizations or projects without preconditions .
- Safe harbor
-
Partial
Stopping at the boundary keeps you covered by Safe Harbor and eligible for the full reward.
- Hall of fame
-
Yes
Monetary rewards aside, vulnerability reporters who work with us to resolve security bugs in our products will be credited on the Leaderboard .
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 8 excluded.
Domains 3
- bc.googleusercontent.com
- google.com
- googleusercontent.com
Products and areas 3
- any Google Cloud product or web service that handles reasonably sensitive user data
- butterfly-net
- [email protected]
Out of scope (8)
- CIDR blocks or IP ranges allocated to Google Cloud customers
- customer instances, databases, storage buckets, or applications
- Google's production environment, Borg
- Google Workspace products
- Recent acquisitions
- Third-party websites
- *.appspot.com
- *.bc.googleusercontent.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Google Cloud VRP's policy. "We" in these lines means the program, not this site.
While testing
-
When investigating a vulnerability, please, only ever target your own accounts.
-
Never attempt to access anyone else's data and do not engage in any activity that would be disruptive or damaging to your fellow users or to Google.
-
No Unauthorized Scanning or Access : Testing, probing, scanning, or interacting with customer instances, databases, storage buckets, or applications without written authorization from the customer is prohibited.
-
Immediate Stop : As soon as a payload, sandbox escape, SSRF, or RPC gives you code execution or access to Borg or Google's internal production network, stop all testing immediately.
-
No Lateral Movement : Do not attempt lateral movement, internal network discovery, credential harvesting, or access to internal services or databases (Spanner, Chubby, etc.).
-
please do not attempt to carry out DoS attacks, leverage black hat SEO techniques, spam people, or do other similarly questionable things.
-
We also discourage the use of any vulnerability testing tools that automatically generate very significant volumes of traffic.
-
Configure your tools with strict target boundaries and rate limits.
-
your testing must not violate any law, or disrupt or compromise any data that is not your own.
Not accepted
-
Cross-site scripting vulnerabilities in “sandbox” domains
-
URL redirection
-
Legitimate content proxying and framing.
-
Bugs requiring exceedingly unlikely user interaction.
-
Logout cross-site request forgery
-
Flaws affecting the users of out-of-date browsers and plugins.
-
Presence of banner or version information.
-
User enumeration.
-
Bypassing the limit of accounts that can be verified with a given SMS number.
-
Activity within the scope of your own provisioned resources.
-
No PoC : Reports that lack a functional proof-of-concept.
-
Customer Misconfiguration / Shared Responsibility
-
UI discrepancy
-
Social Engineering Pre-requisite
-
Vulnerabilities within the third-party product code assessed as S1 severity or lower are not eligible for rewards from the Google Cloud VRP.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 12 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.