Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Legacy API exposes private video titles#111386 | Valid | Information Disclosure | – | 2016-02-10 | – | 1 |
| Private, embeddable videos leaks data through Facebook & Open Graph#121919 | Valid | Information Disclosure | – | 2016-05-21 | – | 3 |
| CRITICAL full source code/config disclosure for Cameo#43998 | Valid | Information Disclosure | – | 2015-05-11 | – | 5 |
| Images and Subtitles Leakage from private videosAnalysed#136850 | Valid | Information Disclosure | – | 2017-10-18 | – | 17 |
| Disclosure of sensitive information through Google Cloud Storage bucketAnalysed#176013 | Valid | Information Disclosure | High | 2017-09-29 | – | 27 |
| All Vimeo Private videos disclosure via Authorization BypassAnalysed#137502 | Valid | Information Disclosure | – | 2016-07-29 | – | 35 |
| Watch any Password Video without passwordAnalysed#155618 | Valid | Information Disclosure | – | 2017-10-18 | – | 44 |
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.