- Top reward
- $31,337
- Top severity paid
- Not published
- Assets in scope
- 5
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $31,337
- top reward, from $500.
- 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
-
$31,337
Supply chain compromises │ $3,133.7 - $31,337 │ $1,337 - $13,337 │ $500 - $3,133.7 │ -
- Lowest reward
-
$500
Other security issues │ $1,000 │ $500 │ - │ -
- Hall of fame
-
Yes
Through this program, we provide monetary rewards and public recognition to researchers who disclose vulnerabilities in Google OSS to us.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
5 assets you may test, 2 excluded.
Source code 2
- public repositories of Google-owned GitHub organizations
- selected repositories hosted on other platforms
Domains 1
- github.com
Products and areas 2
- 3rd-party dependencies
- repository configuration settings (e.g. GitHub actions, access control rules, GitHub application configurations)
Out of scope (2)
- social engineering attacks
- Vulnerabilities in 3rd-party services or platforms used to maintain and build Google OSS (e.g. source code management systems, CI/CD systems, package managers)
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Google Open Source Software VRP's policy. "We" in these lines means the program, not this site.
While testing
-
please send your bug reports directly to the owner of the vulnerable package first and ensure that the issue is addressed upstream before letting us know of the issue details
-
Be shared no earlier than 30 days after the issue was fixed upstream (e.g. a patched software package was released).
-
please do not attempt to carry out DoS attacks, leverage black hat SEO techniques, spam people, or perform other similarly questionable actions.
-
Whenever possible, please try to test the vulnerabilities locally without impacting other users.
-
We also discourage the use of any vulnerability testing tools that automatically generate significant volumes of traffic.
-
Your testing must not violate any law, or disrupt or compromise any data that is not your own.
Not accepted
-
Security vulnerabilities and weaknesses with a root cause in downstream software integration with Google OSS
-
Typosquatting / dependency confusion, unless it can be demonstrated how this leads to a compromise of Google OSS build artifacts distributed to users.
-
Insecure installation / software usage instructions that compromise the security of the developers working on the product
-
Issues with negligible security impact, as described in the Bug Hunter University .
-
social engineering attacks
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.