- Top reward
- $1,000,000
- Top severity paid
- Not published
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $1,000,000
- top reward, from $1.
- Report as the policy says
- The policy page explains how.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- 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
-
$1,000,000
Extreme — Up to $1,000,000
- Lowest reward
-
$1
$1 – $6,000
- Safe harbor
-
Full
Coinbase adheres to and supports the HackerOne Gold Standard Safe Harbor terms.
- Hall of fame
-
Yes
Top hackers
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test, 10 excluded.
Domains 1
- coinbase.com
Products and areas 1
- Web2 products, assets and infrastructure owned by Coinbase
Out of scope (10)
- Ability to abuse existing banking functionality such as ACH or credit card chargebacks
- Demo apps, testnet, staging environments, etc.
- Deprecated open source libraries
- Non-security-impacting UX issues
- Physical security
- Publicly available leaked credentials that have since been rotated
- Rate Limiting (non-critical issues)
- Social engineering
- Username enumeration
- Vulnerabilities in third-party applications that integrate with Coinbase
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Coinbase's policy. "We" in these lines means the program, not this site.
While testing
-
Submit all valid, Coinbase-related bug reports through our programs on HackerOne (for Web2), and Cantina (for Web3).
-
Provide Coinbase a reasonable amount of time to fix a vulnerability prior to sharing details with any other party.
-
Adhere to HackerOne Disclosure Process.
-
Make a good faith effort to preserve the confidentiality and integrity of Coinbase customer data.
-
Do not defraud or attempt to defraud or socially engineer Coinbase customers or Coinbase itself.
-
Do not profit from vulnerabilities outside of Bug Bounty Program payouts.
-
Report vulnerabilities with no conditions, demands, or ransom threats.
Not accepted
-
Social engineering
-
Username enumeration
-
Rate Limiting (non-critical issues)
-
Physical security
-
Non-security-impacting UX issues
-
Deprecated open source libraries
-
Vulnerabilities in third-party applications that integrate with Coinbase
-
Ability to abuse existing banking functionality such as ACH or credit card chargebacks
-
Publicly available leaked credentials that have since been rotated
-
Demo apps, testnet, staging environments, etc.
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 4 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.