- Top reward
- $250,128
- 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,128
- top reward, from $1,000.
- 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,128
A valid bypass of MiraclePtr is now eligible for a reward of $250,128.
- Lowest reward
-
$1,000
A below baseline reward of $1,000 may be issued at the discretion of the VRP panel for reports that do not meet our reporting guidelines, but demonstrate a clear security risk.
- Safe harbor
-
Partial
Of course, your testing must not violate any law, or disrupt or compromise any data that is not your own.
- Hall of fame
-
Yes
we provide monetary awards and public recognition for vulnerabilities responsibly disclosed to the Chrome Browser project.
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, 5 excluded.
Domains 1
- chromium.org
Products and areas 5
- Chrome Browser
- Mali drivers
- Mesa
- PDFium
- Skia
Out of scope (5)
- debugging features
- Experimental features
- MiraclePtr-protected bugs
- unsafe flags
- WebKit that impact Chrome on iOS
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Chrome Vulnerability Rewards's policy. "We" in these lines means the program, not this site.
While testing
-
When investigating a vulnerability, please, only ever target your own computers.
-
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.
-
All security bugs must be reported via Google Bughunters (select -> Chrome VRP) which will apply the correct labels and view restrictions.
-
Reports should adhere to our formatting guidelines to be considered for an award any category.
-
Attach PoCs and traces as individual files
-
Use only Python to serve example files
-
Be reliably reproducible in Chrome, d8 or a supported test binary .
-
Attach a proof of concept (PoC) showing reachability in Chrome or d8
-
Provide clear, concise, and ordered steps to reproduce
-
Specify Chrome versions affected by the bug
Not accepted
-
Generating violative, misleading, or factually incorrect content within the attacker's own session (including standard "jailbreaks" and "hallucinations").
-
AI-generated content-based issues, including reports of AI safety or alignment bypasses.
-
Compliance, legal, or intellectual property issues, including issues relating to country/region-specific laws such as privacy or intellectual property laws.
-
Preamble extraction without sensitive information leakage.
-
Contexts in which a model's incorrect output or classification does not pose a compelling attack scenario or feasible path to user harm.
-
Reports that do not meet our baseline requirements
-
Speculative reports that describe a vulnerability but do not demonstrate that it manifests in Chrome
-
MiraclePtr-protected bugs are no longer considered security issues and are not in scope for VRP rewards.
-
Reports for security bugs introduced in newly landed code on trunk / head within the last seven days are not eligible for VRP rewards.
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 11 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.