Heads up! We appreciate every report, however, please notice that our team is very busy and therefore won't respond to reports which we rate as "low" severity or invalid (e.g. DoS in Apache our "X-Powered-By" headers). So do us and yourself a favour: Don't report such things, we will ignore it.
If you've discovered a security issue with Nextcloud, please read our responsible disclosure policy.
You can then use our HackerOne program to report issues with our supported products. Alternatively, you can contact security (at) nextcloud (dot) com. Your report should include:
- Product version
- A vulnerability description
- Reproduction steps
A member of the security team will confirm the vulnerability, determine its impact, and develop a fix. The fix will be applied to the master branch, tested, and packaged in the next security release. The vulnerability will be publicly announced after the release. Finally, your name will be added to the hall of fame as a thank you from the entire Nextcloud community.
Responsible Disclosure Policy
The Nextcloud community asks that you comply with the following guidelines when researching and reporting security vulnerabilities:- Only test for vulnerabilities on your own install of Nextcloud Server
- Confirm the vulnerability applies to a supported product version
- Share vulnerabilities in detail only with the security team
- Allow reasonable time for a response from the security team
- Do not publish information related to the vulnerability until Nextcloud has made an announcement to the community
Supported Product Versions
See our Security page