Chrome Vulnerability Reward Program (VRP) News and FAQ

[TOC]

News and Updates

Please report all Chromium security bugs in the tracker using this form or https://bughunters.google.com/report/vrp -> Chrome VRP.

Please check here for any news and updates about the Chrome VRP.

• April 2026 : Updates for new reward structure.
• March 2026 : Updated formatting criteria & added self-service hotlists.

About the Program

The Chrome Vulnerability Rewards Program (VRP) is the "security bug bounty" for Google Chrome Browser. Please visit the Chrome VRP Rewards and Policies page for full details.

Top Reporters

• 2025.
• 2024.
• 2023.

Interesting Security Bug Write-Ups

Here are some interesting write-ups of past Chrome security bugs:

• A Bug's Life: CVE-2021-21225
• Exploiting CVE-2021-21225 and disabling W^X
• ZIP embedding attack on Google Chrome extension, by Malcolm Stagg, reporter of CVE-2024-0333

We only post links to articles with the author's consent. Please let us know if you would like your work to be shared here.

Best Practices for Security Bug Reporting

To help make the process of security bug triage as efficient and smooth as possible, please consider the following best practices for Chromium security bug reports:

• Use the security bug reporting form
  • This will allow the bug report to be included in the security bug triage queue immediately.
• Include the version number and OS used to reproduce the bug. For an extra bonus reward, please consider including a bisection.

Proof of Concept (PoC)

• Upload PoC files directly to the report itself as separate attachments.
• Please name the PoC file poc.html or index.html in the case of multiple files.
  • This allows Security Shepherds to run the PoC in ClusterFuzz immediately for triage.
• Ensure the PoC is as minimized as possible.
  • This is useful in root cause analysis and also improves the changes of reproduction by ClusterFuzz or the Security Shepherd triaging your report.
• Please format your PoCs so they do not require running python as root.
  • Your PoC should be constructed to reproduce locally when at all possible.
• Do not provide links to websites (public or unlisted) as PoCs.
  • The PoC should ALWAYS be a file directly attached to the report.
• Example servers should be written only in Python, other languages may lead to your report being rejected.

Patches to simulate a compromised renderer

• Instead of providing a patch, use MojoJS to simulate a compromised renderer.
  • Otherwise, explain why MojoJS is not sufficient.
• Upload a git generated patch with a clear base commit.
• Use process guards (e.g. test the commandline for --type="renderer") if code can run in multiple processes.
• Use Sleep() in privileged processes to simulate a race.
• Do not add extraneous logging like LOG(INFO) << "EXPLOIT SUCCEEDED".

Steps to Reproduce

• Please include clear, concise, numbered steps to reproduce the bug you are reporting.
• Provide the full Chrome or d8 command line and any build flags to reproduce.
  • avoid --enable-experimental-web-platform-features and --enable-unsafe-webgpu and instead provide specific feature flags.
• Do not run Chrome in a harness or via CDP.

Report Attachments

• Do not upload attachments as a single compressed file, such as .zip, .gzip, or .tar files.
  • Please upload all necessary attachments (PoCs, patch, fix patches, video demonstrations, exploits) as individual files on the bug report.
• ASAN stack traces should be symbolized, and include all additional information fields, and the sanitizer should be built using Chrome's standard mitigation and hardening flags.
• Patch.diff files that are not suggested fixes should explain - as part of the steps to repro - the reason for the patch, such as to simulate a compromised renderer or allow for stable reproduction, such as running the PoC in a loop or winning a race condition.
• Do not provide links (public or unlisted) to demonstration videos.
  • If possible, please upload your demonstration video directly to the report.
  • Please keep the video as concise as possible.
    • We do not need to see you loading Chrome or displaying the version page multiple times in a video.
  • DO feel free to include music, sound effects, or animal pics in your videos. :)

Test Harnesses

• Do not provide a custom test harness.
• Do not modify browser or unittests.
• Do not run Chrome with a harness, debugging client or shell script.
• Chrome provides some test binaries you can use directly:
  • chrome
  • d8 (but do not supply experiment features)
  • pdfium_test

Bug Reporting

• Please ensure your report is concise and clearly articulates the bug, explaining and demonstrating (through PoC, exploit, and/or video), such as:
  • How the issue is reachable and exploitable by web content or a compromised renderer.
  • The security consequences / user harm resulting from exploitation of the bug.
• Avoid reporting theoretical bugs: reports that simply state a potential bug from static analysis without demonstration of the security issue.
  • These reports will be considered as unactionable and will be closed as WontFix (Not reproducible).
• At a minimum, please include the version number and release channel (Stable/Beta/Dev) on which you discovered and reproduced the issue you are reporting.
  • For a full reward, please consider performing a full bisection, detailing the commit that introduced the issue and / or all the active release channels impacted by the bug.
• Empty initial comments will lead to your report being closed and may lead to your account being suspended. Do not create placeholder issues.

Demonstrating controlled read or write

Mojom interfaces to demonstrate controlled reads or controlled writes in privileged processes are available in vrp_flags.mojom.

To prove a controlled read or write you must attach a small json file vrp-flag.json to your report:

{
  "flag": "read",
  "params": {
    "process": "browser",
    "poc": "poc-read.html",
    "chrome_version": "123.6789.0.1",
    "os": "win",
    "arch": "x64",
    "command_line": ["--enable-features=FeatureName", ...],
  }
}

• attach a minimized poc.html that triggers the bug under ASAN
• attach an additional poc-read.html or poc-write.html
• provide additional command line arguments needed to run the poc
• provide the full version of the released version of Chrome the poc targets
• provide the operating system the poc targets
• provide the process the poc targets

poc-read.html or poc-write.html will be loaded from a local server, with mojojs files available under /gen/. If your poc reliably hits the VRP flag, your report will be eligible for the controlled read or controlled write reward.

If the controlled read or write is not reproducible or not reliable, but the minimized poc does trigger an ASAN report, your issue will receive the standard reward.

The controlled read or controlled write poc must be included in your initial report - we will not consider submissions added at a later time.

Your poc must target a released version of Chrome Stable, Beta or Dev. We will not accept submissions that target Canary or local builds.

At this time we do not accept controlled read/write submissions that patch the renderer or that require multiple files or servers to demonstrate an issue.

Supported operating systems and architectures (with default hardware mitigations enabled):

• win - Windows 11 on x64 or ARM64
• mac - The latest release of MacOS on ARM64
• linux - The latest release of Debian stable w/wayland on x64 or ARM64

Non-standard, debugging or unsafe command line flags and features are not accepted.

Frequently Asked Questions (FAQ)

Scope / Reward Eligibility

What features are definitively out of scope?

This list is not exhaustive but should help reporters focus on issues in Chrome:

• V8 features marked as Experimental. Security bugs that are specific to V8 Experimental features are not eligible for Chrome VRP rewards. The experimental status of a V8 feature will be denoted in the flag definition in source code, in the flag description in the help menu, or via a printed message at runtime.
• Swiftshader is deprecated and only supported for limited test and debug environments.
• WebNN is not enabled and undergoing security hardening. It is not eligible for the VRP at this time.
• Unsafe Flags. Any flags which show a warning infobar that they present a risk to the user are not in scope. These flags are intended for testing and debugging only.
• --single-process mode is purely for test and debugging and can lead to races and ownership issues that do not manifest in multi-process mode.

How do I know if my bug report is possibly eligible for a VRP reward?

• All validated, qualifying vulnerability reports are automatically considered for a reward once they are accepted. At which point you will see the reward-topanel hotlist signifier added to your bug report. This indicates that it will be reviewed at a Chrome VRP panel meeting for a reward decision.
• The bug will be updated again once the panel has made a reward decision.

I want to report a bug through a broker / not directly to Chrome.

• We believe it is against the spirit of the program to privately disclose security vulnerabilities to third parties for purposes other than fixing the bug. Consequently, such reports will not qualify for a reward.

What if someone else reported the same bug?

• Only the first actionable report of a security bug that we were previously unaware of is eligible for a potential VRP reward. In the event of a duplicate submission, the earliest actionable report in the tracker is considered the first report.
• If the issue is discovered by one of our internal tools within seven days of your report, it is considered a known issue and is not eligible for a reward.

What does actionable report mean?

• A security bug report is only considered actionable once it contains appropriate information that allows for validation and triage, such as a minimized test case / PoC, steps to reproduce, a symbolized stack trace, and/or other demonstrable evidence of the security bug being reported.
• A report lacking this actionable information and does not allow us to reproduce the issue to validate and investigate the bug is not considered to be a complete, actionable submission.

Are bugs in unlaunched features / behind command line flags VRP-eligible?

• Yes, we are interested in bugs in any code that has shipped to even a fraction of our users.
• The only exception at this time are security bugs in V8 behind --experimental; this flag is for early and experimental V8 development efforts and this configuration should not be used in production. Security bugs specific to this configuration are not eligible for Chrome VRP rewards.
• Please ensure you include what command line flags are required to trigger the bug in your report and remove any unnecessary flags.
• The report will be triaged with the appropriate security severity and as Security_Impact-None. This categorization of Security_Impact-None does not impact the potential reward amount.
• Please note that these security bugs do not have the same SLO to fix as bugs impacting Stable, Beta, or Dev. The only expectation is that the bug is fixed before the feature is exposed to users, such as part of an origin trial or field experiment.

What about bugs in channels other than Stable?

• We are interested in security bugs in Stable, Beta, and Dev channels because it's best for everyone to find and fix security bugs before they impact Stable channel users.
• We do, however, discourage hunting in Canary or Trunk builds. These do not go through release testing and exhibit short-lived regression that are typically identified and fixed quickly. Reports of bugs in new code in trunk may collide with on-going work of the engineers as part of "trunk-churn".
• Reports for bugs in newly landed code on Trunk / Head landed within seven days of the report are not eligible for VRP rewards.

Are bugs in third-party components in scope and eligible for VRP rewards?

• Yes, we are interested in reports for bugs in our third-party components, such as libxml, sqlite, and image and compression libraries. The security impact must manifest in and result in security consequences in shipped configurations of Chrome.
• Reports should demonstrate that the vulnerable code is reachable in Chrome.
• We are interested in rewarding any information that enables us to better protect our users. In the event of bugs in an external component (such as an upstream dependency), we may also ask that you file a bug directly with the vendor or maintainer for that component, so that the product or project owners can set about fixing the bug immediately.
• This also ensures that you have direct access to the status of the report, can directly communicate with that vendor or project owner, and receive credit or acknowledgement (if they have such a mechanism to do so).

Can I submit my report(s) and provide a working exploit or proof of r/w later?

• Most definitely! We realize that developing an exploit is a lengthy process and we very much encourage this approach, as it allows us to work on fixing the bugs as soon as possible. It also reduces the chance that someone else reports the same issue while you are working on the exploit.
• The exploit must work against a released Chrome build on the latest operating system versions and architectures, and prove code execution by executing a command shell with the credentials of the user running Chrome.
• r/w and arbitrary read must work using Chrome in a special mode - details will be released here soon.
• If you have a proof to add to a bug after it has been rewarded, add the hotlist Security-Request-Exploit-Assessment (hotlist id:8186895) along with a poc and comment that demonstrates the proof. We will review this queue roughly weekly.

Is there a time limit for submitting an exploit?

• Although we don't have a set time limit, we would expect that the exploit would follow within four weeks of the initial report.
• The number of exploit bonuses is capped and priority for exploit bonuses will be taken from the time an exploit is added to an issue, and the hotlist Security-Request-Exploit-Assessment is added.

Will you reward for types of bugs that are not specifically listed?

• Yes. We are interested in rewarding any information that enables us to better protect Chrome users. Reward amounts are based on the potential security harm of the bug being reported and the quality of the report.

Report Status / Bug Lifecycle

What happens after I report a security bug to you?

• Please see Life of a Security Issue.

My bug was triaged incorrectly?

• We are human. If you disagree with the severity assessment of an issue please comment on the issue and add it to the Security-Severity-Reassessment-Request hotlist (id:8059196) which will enter the issue into a queue that is reviewed on a weekly basis by the security team. Access to the hotlist is restricted to people on our VRP Updates List. If you do not have permission to add the hotlist please ask on the bug and a Chromium team member can add it for you.

My bug was Fixed and the team hasn't marked it Fixed?

• Identify when the issue was fixed. You can use git bisect or Chromium's bisect-builds.py to help locate when the issue went away. Add this evidence to the bug, ideally identifying the CL which fixed the issue.
• Give the team a week to close the issue themselves.
• If, after a week, the issue is still open, add it to the Security-Fixed-Issue-Request hotlist (id:8059017) where it will be addressed by the security team on a weekly basis.

Will I receive a CVE for my bug?

• If the issue you report was an exploitable security bug impacting Stable or older version of Chrome, and it was the first actionable report of that issue, your bug will be issued a CVE at the time the fix ships in a Stable channel update of Chrome.
• The CVE number will be updated directly on the report itself and listed in the Chrome Browser release notes for that Stable channel update.

Disclosure / Report Visibility

What if I disclose the bug publicly before you have fixed or disclosed it?

• Please read our stance on vulnerability disclosure
• Essentially, our pledge to you is to respond promptly and fix bugs in a sensible timeframe, and in exchange, we ask for a reasonable notice of potential disclosure.
• Disclosures that go against this principle will usually not qualify for a VRP reward, but we will evaluate them on a case-by-case basis.

When will the bug I reported be publicly disclosed?

• Most security bugs are automatically opened for public access 14 weeks after the bug is closed as Fixed, meaning the fix commit is landed on Chromium main.
• Our automation removes the view restrictions, opening the report for public visibility at that time.

Can you keep my identity confidential from the public?

• Your email address is obscured by default (by elision) in the Chromium bug tracker and is not revealed once the bug is publicly disclosed.
• If you do not want to receive public acknowledgement for your report, please let us know in the report or before the issue is listed in the release notes.
  • We will credit the finding to "anonymous" researcher or we are happy to credit it to whatever pseudonym or tag you provide to us.
• If you receive a VRP reward for your report and accept it, Google or Bugcrowd (depending on who you select to process your VRP reward) will need to privately collect some identifying information to process your reward payment.

Can you keep my report under Security Embargo?

• Security Embargo prevents issues from being disclosed beyond the security team and engineers working to resolve the bug. Once the issue is fixed, the (Security Notify) community of embedders and developers of other Chromium-based products are reliant on the access to bug reports. Because Security Embargo restricts this access indefinitely, it is used only on a specific case-by-case basis, such as when the bug should never be publicly disclosed.

Rewards / Reward Decisions

My bug was rewarded under older amounts, will you pay the difference?

• We often increase reward amounts and introduce new bonus opportunities. We reward bug reports based only on the rules that were in effect at the time of bug submission and VRP Panel assessment.

The exploit market pays more for bugs!

• Yes, we are aware that the exploit brokers, underground markets, three cats in a trenchcoat on your local street corner may pay more for bugs. We understand that many pockets of society may pay you more money to purchase information about the vulnerabilities you may find or exploits you develop. These people buy vulnerabilities and exploits for offensive purposes to target people using Chrome across the internet. We believe the reward you get under those circumstances comes with strings attached -- including buying your silence and accepting that any bug you sell may be used to target other people without their knowledge, such as activists, dissidents, and vulnerable populations.
• We understand our reward amounts may be less than these alternatives, but we also believe we provide additional benefits when reporting directly to us, such as public acknowledgement of your findings and skills, the opportunity to engage directly with the security team and engineers working to resolve your bug, a quick resolution and seeing a fix you contributed to go out into the world, the opportunity to publicly discuss/blog/present/share your amazing work, and the knowledge that you are helping keep Chrome secure for billions of people across the world!
• Also, many of our researchers receive gifts of swag and are invited to events.
• You'll additionally have the peace of mind to know your bug findings were never used by shady people for nefarious purposes.

I provided a new POC or new information-- will you increase the VRP reward?

• Not generally, unless there are expectional circumstances. Criteria for Chrome VRP reward decisions is inclusive of information included in the initial report to the time the bug is fully resolved. Information that is provided after the bug is resolved and assessed by the VRP does not benefit the effective and efficient investigation and fix of the bug and should not be expected to impact VRP reward assessment or reassessment.
• We want to incentivize the earliest reporting of security issues, however, security bug reports should only be submitted once they are fully inclusive of all necessary aspects of a security bug report to allow for validation triage, and resolution. If you can demonstrate an issue is not mitigated or can be reliably reproduced and triggered remotely, that should be demonstrated as part of the initial report or within the period of investigation and fix.
• We do, however, welcome reports of a functional exploit after the report is submitted and even resolved for a potential higher VRP reward.

When will I receive my reward?

• Once the bug has been assessed by the VRP Panel, the bug report is updated with a reward decision and information.
• There are two options for payment of a VRP Reward -- direct through Google or through Bugcrowd.
  • Through Google:
    • If this is your first VRP reward for a Google program, a member of the finance p2p-vrp team will reach out to enroll you in the Google payment system.
    • VRP payments are handled by the p2p-vrp finance team. Once you have been enrolled, you will receive you payment within 1-2 weeks of a reward decision.
    • Please reach out to [email protected] with questions about the payment enrollment process or assistance with any payments issues.
  • Through Bugcrowd (preferred):
    • You must already have or create a new Google Bughunters profile. (Please note, you can set your Bughunters profile to be private if you prefer to not have a public profile).
    • Associate your Bughunters profile with the email address you use for reporting Chrome security issues.
    • Have a Bugcrowd account or register with Bugcrowd.
    • In your Bughunters profile change your Payment Options from Legacy to Bugcrowd and enter the email address for your Bugcrowd account (and hit Save)!
    • Future reward payments will be sent to Bugcrowd for processing and you will receive an email directly from Bugcrowd to accept those rewards.
• If at any point you want to change the method by which you receive VRP reward payments, this can be done through your Google Bughunters profile > Payments Options:
  • Select Legacy to receive your payments through Google p2p payments processing.
  • Select Bugcrowd to select payments through Bugcrowd. Remember you must register with Bugcrowd first and enter your Bugcrowd account email in your Bughunters profile.

I don't agree with the reward amount. Can I get the reward reassessed?

• We try our best to be fair and consistent, but sometimes we miss something in our assessment. If you feel that is the case please add a comment explaining your position to the issue and add the Security-VRP-Reassessment-Request hotlist (id:8186354).

Updates On The VRP

Request to join our low volume list.

Other

I have a security-related question that is not listed here.

• This is a statement not a question, but we're happy to help. Take a look at the Chrome Security FAQ to see if your question is answered there.
• Also, if you have not already, please check the Chrome VRP Rewards and Policies page.
• If you still need assistance, please reach out to [email protected].