Brave Software bug bounty programs
brave.com Updated
Brave Software runs three public programs: a HackerOne bug bounty paying up to $10,000, a Sorona bug bounty paying up to $1,250 and a Sorona bug bounty paying up to $1,250.
- Top reward
- $10,000
- HackerOne
- Programs
- 3
- 3 pay cash
- Targets in scope
- 23
- 6 types, deduplicated
- Last change
- None yet
- Tracked since Nov 2026
Where to report
3 programs, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.
Start here
Brave Software
HackerOne · Pays the most of the 3 programs: up to $10,000.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
Brave Software
HackerOne · Bug bounty |
$10k (highest) | $1,000 | $250 | $100 | $10,000 | Partial | – | 13 hours average | Open |
|
Brave Browser
Sorona · Bug bounty |
– | $1,250 (highest) | $313 (highest) | $125 (highest) | $1,250 | Partial | – | 7 hours promised | Open |
|
Brave Search MCP Server
Sorona · Bug bounty |
– | $1,250 | $313 | $125 | $1,250 | Partial | – | 24 hours promised | Open |
-
- Critical
- $10k (highest)
- High
- $1,000
- Medium
- $250
- Low
- $100
- Safe harbor
- Partial
- First response
- 13 hours average
-
- Critical
- –
- High
- $1,250 (highest)
- Medium
- $313 (highest)
- Low
- $125 (highest)
- Safe harbor
- Partial
- First response
- 7 hours promised
-
- Critical
- –
- High
- $1,250
- Medium
- $313
- Low
- $125
- Safe harbor
- Partial
- First response
- 24 hours promised
Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
23 targets across all 3 programs, each listed once with the programs that cover it. 14 excluded.
-
https://github.com/brave/*, https://github.com/brave-intl/*
Source code Critical
Covered by HackerOne
-
Brave's AI and agent features, covered by a policy section the changelog added on 2025-11-26
Products and areas
Covered by Brave Browser
-
Brave's declaration is a repository wildcard: security or privacy issues in any repository owned by github.com/brave or github.com/brave-intl that is neither forked nor archived. The program carries it as a single source-code asset, bounty-eligible at critical maximum severity
Products and areas
Covered by Brave Browser
-
Brave's web properties, carried at critical maximum severity: search.brave.com, account.brave.com, talk.brave.com, api-dashboard.search.brave.com, and the Creators and Ads dashboards behind the Brave websites asset row
Products and areas
Covered by Brave Browser
-
brave-intl/bat-client and brave-intl/bat-publisher, which the program names individually alongside the org-wide wildcard
Products and areas
Covered by Brave Browser
-
brave/brave-core, listed again as an asset in its own right. That is the engine layer, the whole patch set Brave lays over Chromium, and the whole of it is in scope
Products and areas
Covered by Brave Browser
-
Everything else the same declaration covers, on the same reward row: Brave's other repositories, the desktop and mobile browser builds, and Brave's web properties, api-dashboard.search.brave.com among them, the dashboard that issues the keys these installs hold
Products and areas
Covered by Brave Search MCP Server
-
Its API-key handling: anywhere the Brave Search key can be read by an unintended party, written into a log, echoed back inside a tool result, or sent to a host it was never meant to reach
Products and areas
Covered by Brave Search MCP Server
-
That repository in full, across both the stdio transport desktop clients spawn and the HTTP transport used when the server runs as a network service
Products and areas
Covered by Brave Search MCP Server
-
The HTTP transport's own request handling, covering authentication, origin checks and session binding, when the server is reachable by something other than the local client that spawned it
Products and areas
Covered by Brave Search MCP Server
-
The product surfaces Brave adds on top of Chromium: Shields and the adblock-rust engine behind it, Rewards, Wallet and the BAT contract addresses the policy lists, Tor windows, and sync
Products and areas
Covered by Brave Browser
-
The program's declaration is a repository wildcard: any non-forked, non-archived repository under github.com/brave or github.com/brave-intl, carried as one source-code asset at critical maximum severity. brave/brave-search-mcp-server is one of them
Products and areas
Covered by Brave Search MCP Server
-
The response path that hands search results back to the host agent, where attacker-controlled page content crosses into an agent's context
Products and areas
Covered by Brave Search MCP Server
-
The shipped clients, each an asset of its own: Brave Browser Desktop on the latest nightly, beta or stable build, com.brave.browser and com.brave.browser_beta on Google Play, and com.brave.ios.browser on the App Store
Products and areas
Covered by Brave Browser
-
The tool surface it exposes to MCP clients, including argument parsing and parameter validation, and anything that lets a caller reach a capability or endpoint the server did not intend to expose
Products and areas
Covered by Brave Search MCP Server
No target matches. Try part of a host name, such as the company name.
Out of scope 14
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
brave.com itself, where the program says it is not generally interested and does not guarantee a response, reserving consideration for severe bugs that threaten immediate user harm
Brave Browser
-
Chromium-inherited issues, which Brave routes to the Chromium team rather than paying for here
Brave Search MCP Server
-
Denial of service and resource exhaustion in the client products, unless you can carry it through to code execution or data disclosure
Brave Browser
-
Denial of service bugs, which the dated policy changelog entries place out of scope
Brave Search MCP Server
-
Fingerprinting and cross-site tracking methods in general, and detection that a user is running Brave rather than Chrome
Brave Browser
-
Forked and archived repositories under either GitHub organisation, which the wildcard scope carves out by name
Brave Browser
-
Forked and archived repositories under either GitHub organisation, which the wildcard scope carves out explicitly
Brave Search MCP Server
-
GitHub wikis being publicly editable, which is a known and accepted configuration
Brave Search MCP Server
-
Non-default browser extensions and social media account takeovers
Brave Search MCP Server
-
Non-default extensions, self-XSS, login and logout CSRF, and anything that needs physical access to the device
Brave Browser
-
Prompt engineering that only produces an undesirable model response, with no data leakage or unauthorised action to show for it
Brave Search MCP Server
-
Releases other than the current ones: the desktop asset row takes issues in the latest nightly, beta and stable builds only
Brave Browser
-
The legacy Muon-based browser, the Muon framework itself, and all LinkBubble products
Brave Browser
-
Upstream Chromium bugs that Brave will simply inherit a fix for. They qualify only when Brave fixes them directly, which the policy itself calls very rare
Brave Browser
Recent changes
Reward and scope changes across every Brave Software program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
Recent CVEs
Published vulnerabilities in Brave Software products, from the NVD.
-
CVE-2023-52263 Medium
Brave Browser before 1.59.40 does not properly restrict the schema for WebUI factory and redirect. This is related to browser/brave_content_browser_client.cc and browser/ui/webui/brave_web_ui_controller_factory.cc.
-
CVE-2023-52263 Medium
Brave Browser before 1.59.40 does not properly restrict the schema for WebUI factory and redirect. This is related to browser/brave_content_browser_client.cc and browser/ui/webui/brave_web_ui_controller_factory.cc.
-
CVE-2023-52263 Medium
Brave Browser before 1.59.40 does not properly restrict the schema for WebUI factory and redirect. This is related to browser/brave_content_browser_client.cc and browser/ui/webui/brave_web_ui_controller_factory.cc.
-
CVE-2023-28364 Medium
An Open Redirect vulnerability exists prior to version 1.52.117, where the built-in QR scanner in Brave Browser Android navigated to scanned URLs automatically without showing the URL first. Now the user must manually navigate to the URL.
-
CVE-2023-28364 Medium
An Open Redirect vulnerability exists prior to version 1.52.117, where the built-in QR scanner in Brave Browser Android navigated to scanned URLs automatically without showing the URL first. Now the user must manually navigate to the URL.
-
CVE-2023-28364 Medium
An Open Redirect vulnerability exists prior to version 1.52.117, where the built-in QR scanner in Brave Browser Android navigated to scanned URLs automatically without showing the URL first. Now the user must manually navigate to the URL.
-
CVE-2023-28360 Medium
An omission of security-relevant information vulnerability exists in Brave desktop prior to version 1.48.171 when a user was saving a file there was no download safety check dialog presented to the user.
-
CVE-2023-28360 Medium
An omission of security-relevant information vulnerability exists in Brave desktop prior to version 1.48.171 when a user was saving a file there was no download safety check dialog presented to the user.
About this page
This page gathers every public program listed under brave.com: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.
Something wrong or missing? Report a correction.