Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Monero

By The Monero Project Vulnerability disclosure program on HackerOne getmonero.org

Accepting reports
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on HackerOne
Submit through the program page.
Paid by XMR
No identity requirement stated.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Pays cash
Yes Provide an XMR address within the report if you wish to receive bounty (assuming that the report is valid)

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

1 asset you may test, 5 excluded.

Source code 1

  • the Monero applications, which are written in C++, with some C and assembly, and QtQuick for the Monero GUI
Out of scope (5)
  • CSRF / XSS RELATED REPORTS
  • metadata leaks from volunteer hosting infrastructure
  • The live sites
  • the Monero forum
  • website vulnerabilities

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Monero (via HackerOne)'s policy.

While testing

  • Provide an XMR address within the report if you wish to receive bounty (assuming that the report is valid)
  • The live sites are NOT in scope, only the code is!

Not accepted

  • CSRF / XSS RELATED REPORTS
  • website vulnerabilities
  • metadata leaks from volunteer hosting infrastructure
  • low-hanging fruit like CSRF / XSS bugs

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour 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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

The Monero Project

  1. Read and abide by our Vulnerability Response Process
  2. Provide an XMR address within the report if you wish to receive bounty (assuming that the report is valid)
    • PoC within a report will most likely result in more bounty than not

Scope

!!! DO NOT SUBMIT CSRF / XSS RELATED REPORTS. THEY WILL BE CLOSED AS NOT APPLICABLE !!!

This primarily exists to help us find critical vulnerabilities in the Monero applications, which are written in C++, with some C and assembly, and QtQuick for the Monero GUI. We are not terribly interested in website vulnerabilities (the Monero site use Jekyll and produces static HTML) or metadata leaks from volunteer hosting infrastructure.

If you are looking to disclose web app vulnerabilities, or low-hanging fruit like CSRF / XSS bugs, you are looking at the wrong project. These are not web apps!

Project-specific policies:

Only the projects listed in our Vulnerability Response Process are considered in scope.

Other projects, such as the Monero forum, are either being deprecated or are out of scope.

Note: as a pro-privacy project we have volunteers running copies of the websites on hidden services on Tor and I2P, as well as on multiple public domains. The live sites are NOT in scope, only the code is!