Monero · disclosed reports
Memory Corruption
8 disclosed reports · $0 paid · 8 valid
Every dot is a report; the named ones are the most upvoted. Bright dots were paid a bounty. Reports open on HackerOne. The status is HackerOne's own outcome; "access needed" is only what a title states.
Open Monero on HackerOne- reports
- 8
- valid
- 8
- paid a bounty
- 0
Every one of the 8 is a mark on the map. Named now: 1 to 8, most upvoted first.
- wallet-rpc crash via malformed /gettransactions response (empty txs → vector::front() in check_tx_key / check_tx_proof)
- Reported RPC Overflow
- wallet-rpc describe_transfer uses real_output_in_tx_index instead of real_output: cold-wallet pre-sign review shows wrong ring member
- Array Index Underflow--http rpc
- Buffer out of bound read in miniupnpc xml parser
- Stack Overflow in JSON RPC Server
- Potential use-after-free due to struct array_entry_t lacking an explicit copy constructor
- Out-of-bounds read when importing corrupt blockchain with monero-blockchain-import
paid a bounty
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-14. CVE List through 2026-11-14 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-14. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data. Use this via MCP