Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Improper authorization on `/api/as/v1/credentials/` allows any App Search user to access all API keys and escalate privileges#1168528 | Valid | Access Control | High | 2021-06-02 | – | 13 |
| Remote Code Execution in coming Kibana 7.7.0Analysed#861744 | Valid | Access Control | Critical | 2021-04-19 | $5,000 | 14 |
| Improper authorization on `/api/as/v1/credentials/` for Dev Role User with Limited Engine AccessAnalysed#1218680 | Valid | Access Control | High | 2021-08-03 | – | 21 |
| RCE hazard in reporting (via Chromium)Analysed#1168765 | Valid | Access Control | Critical | 2021-05-26 | $10,000 | 25 |
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.