Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Path traversal leading to limited CSRF on GET requests on two endpointsAnalysed#301862 | Valid | No weakness recorded | – | 2019-04-05 | – | 41 |
| Internal machine learning API endpoint for CWE classification is vulnerable to path traversalAnalysed#2032778 | Valid | File and Path Handling | Medium | 2023-07-05 | – | 33 |
| File Name EnumerationAnalysed#33935 | Valid | Information Disclosure | – | 2014-11-17 | – | 17 |
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, where there is one, which can be wrong. Data as of 2026-11-15.