- Top reward
- $300,000
- Top severity paid
- Not published
- Assets in scope
- 4
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $300,000
- top reward, from $360.
- Report as the policy says
- The policy page explains how.
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
-
$300,000
A) Arbitrary Code Execution │ $300,000 │ $150,000 │ $15,000 │ $9,000
- Lowest reward
-
$360
C) Other Vulnerabilities │ $3,600 │ $1,350 │ $675 │ $360
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 6 excluded.
Android apps 4
- AGSA
- Gmail
- Google Cloud
- Google Play Services
Out of scope (6)
- Attacks that require a rooted device
- Hardcoded API keys
- Secondary lockscreen bypasses
- Variants of Strandhogg and Tapjacking
- Vulnerabilities that allow access to non-sensitive media in external storage
- Vulnerabilities that do not work on the latest available operating system version
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Google Mobile VRP's policy.
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.
-
Your testing must not violate any law, or disrupt or compromise any data that is not your own.
Not accepted
-
Certain common low-risk vulnerabilities deemed trivially exploitable.
-
Vulnerabilities that allow access to non-sensitive media in external storage
-
Variants of Strandhogg and Tapjacking
-
Vulnerabilities that do not work on the latest available operating system version
-
Hardcoded API keys
-
Attacks that require a rooted device
-
Secondary lockscreen bypasses
-
attack scenarios that require an unreasonable amount of user interaction or social engineering
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.