Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Exploitable vulnerability in SDEX#330105 | Valid | Input Validation and Logic | – | 2018-10-14 | – | 29 |
| It's possible to put SDX orderbook into invalid state and execute trades at arbitrary price#321511 | Valid | Input Validation and Logic | – | 2018-10-14 | – | 12 |
| heap-buffer-overflow (READ of size 1) in cpptoml::parser::consume_whitespace()#240659 | Valid | Memory Corruption | – | 2017-06-30 | – | 8 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (348 analysed so far), which can be wrong. Data as of 2026-11-14.