Technical

Bug Bounty

Financial reward program an organization offers to security researchers who discover and report vulnerabilities in its systems.

Scarabée mécanique en métal noir aux pattes articulées enfermé sous un dôme de verre, une pièce de monnaie bordeaux posée juste à côté sur un sol sombre réfléchissant, faisceau de lumière venant du haut
Bug bounty — Image générée par IA (Qwen-Image 2.1, ComfyUI local)

A bug bounty is a financial reward program offered by an organization (company, open source project, government agency) to independent security researchers (ethical hackers) who discover and responsibly report vulnerabilities in its systems. HackerOne paid out $81 million in rewards between July 2024 and June 2025, with a cumulative total of more than $300 million since the platform was founded.

Technical definition

How it works and who is involved

A bug bounty program defines a scope of testable systems, a reward grid by severity (from Low to Critical, with amounts rising steeply with the severity of the flaw), and rules of engagement (no denial of service, no access to user data, testing only on authorized environments).

Intermediary platforms (HackerOne, Bugcrowd, and YesWeHack in Europe) structure the ecosystem: researcher identity checks, report triage, payment handling and mediation. They host public programs (any researcher can take part) and private ones (invitation only, for sensitive targets).

Responsible disclosure

The responsible disclosure process imposes a delay between the private report and public release, giving the vendor time to fix the issue. The standard is 90 days (Google Project Zero). If the vendor has not fixed it within that window, the researcher may publish. This mechanism pushes vendors to react quickly: a CVE published with an exploit before a patch exists is a critical risk.

Current challenges

Bug bounties and open source projects

Major open source projects (Linux, Kubernetes, Chrome, Firefox) have bug bounty programs funded by foundations or sponsors. Smaller community projects (such as OpenClaw) often have none for lack of budget, which creates a security blind spot. The Huntr initiative and the GitHub Security Lab program try to fill this gap for critical open source projects.

A maturity indicator in due diligence

In an M&A context, the existence of a bug bounty program is a strong positive signal: it shows that the organization takes security seriously, has a remediation process, and maintains a constructive relationship with the security community. Its absence, as in the OpenClaw case ("security is not a priority," according to its creator), is a risk indicator that must be offset by a post-acquisition remediation budget.

Standards and Specifications

ISO/IEC 29147:2018

Guidelines for vulnerability disclosure

CERT/CC Vulnerability Disclosure Policy

Carnegie Mellon CERT's framework for coordinated responsible disclosure

Frequently Asked Questions

How does a bug bounty program work?

The organization defines a scope: which systems may be tested, which types of vulnerabilities it is looking for, and the rewards attached to each severity level (informational, low, medium, high, critical). Security researchers (ethical hackers) test the systems within that framework and submit detailed reports.

The organization's security team sorts the reports (triage), validates the vulnerabilities, fixes them, then pays the reward. Intermediary platforms (HackerOne, Bugcrowd, YesWeHack) run the process: researcher identity checks, initial triage, payment, and mediation in case of dispute. How long a full cycle takes depends on the severity of the flaw and on how quickly the team in charge of the fix responds.

How much does a bug bounty program cost?

The annual budget varies widely with the size of the organization and the type of program: a private program open to a handful of invited researchers costs far less than a large enterprise's public program (Google, Microsoft, Apple). On top of the rewards paid out come the fees of the intermediary platform.

The ROI is favorable: even a large reward for a critical flaw is modest compared with the average cost of a data breach ($4.88M according to the IBM Cost of a Data Breach Report 2024). Google paid out nearly $12M in rewards in 2024 through its Vulnerability Reward Program, according to Google's annual review.

Why is the lack of a bug bounty a red flag in due diligence?

A software project with neither a bug bounty program nor a responsible disclosure policy signals low security maturity. Researchers who find a flaw have no official channel to report it, which raises the risk of uncoordinated public disclosure (full disclosure) or silent exploitation.

In the OpenClaw case, the lack of a bug bounty contributed to a pile-up of critical CVEs. Researchers had to publish their findings through unofficial channels, creating public pressure instead of a coordinated fix process. In due diligence, it is a sign that security is not a priority for the organization.

Resources and Documentation