Skip to content

Nextcloud

By Nextcloud GmbH Bug bounty on HackerOne nextcloud.com

Accepting reports
Top reward
Not published
Top severity paid
Critical
Assets in scope
94
Public CVEs
60
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report on HackerOne
Submit through the program page.
Publish after a fix
Coordinate the timing with the company.

Rewards

What HackerOne lists as the payout for each severity.

HackerOne does not publish a reward table for this program.

Pays cash
No Please note that Nextcloud does not offer monetary bounties for security reports submitted through this program.
Hall of fame
Yes Public acknowledgment on the HackerOne platform

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

94 assets you may test, 8 excluded.

Source code 63

  • https://github.com/nextcloud/collectives Critical No bounty
  • https://github.com/nextcloud/files_confidential Critical No bounty
  • https://github.com/nextcloud/tables Critical No bounty
  • https://github.com/roundcube/roundcubemail Critical No bounty
  • nextcloud/3rdparty Critical No bounty
  • nextcloud/activity Critical No bounty
  • nextcloud/approval Critical No bounty
  • nextcloud/bruteforcesettings Critical No bounty
  • nextcloud/calendar Critical No bounty
  • nextcloud/calendar_resource_management Critical No bounty
  • nextcloud/circles Critical No bounty
  • nextcloud/contacts Critical No bounty
  • nextcloud/data_request Critical No bounty
  • nextcloud/deck Critical No bounty
  • nextcloud/end_to_end_encryption Critical No bounty
  • nextcloud/external Critical No bounty
  • nextcloud/files_accesscontrol Critical No bounty
  • nextcloud/files_antivirus Critical No bounty
  • nextcloud/files_automatedtagging Critical No bounty
  • nextcloud/files_fulltextsearch Critical No bounty
  • nextcloud/files_fulltextsearch_tesseract Critical No bounty
  • nextcloud/files_lock Critical No bounty
  • nextcloud/files_pdfviewer Critical No bounty
  • nextcloud/files_retention Critical No bounty
  • nextcloud/files_rightclick Critical No bounty
  • nextcloud/files_texteditor Critical No bounty
  • nextcloud/firstrunwizard Critical No bounty
  • nextcloud/flow_notifications Critical No bounty
  • nextcloud/fulltextsearch Critical No bounty
  • nextcloud/fulltextsearch_elasticsearch Critical No bounty
  • nextcloud/globalsiteselector Critical No bounty
  • nextcloud/groupfolders Critical No bounty
  • nextcloud/guests Critical No bounty
  • nextcloud/logreader Critical No bounty
  • nextcloud/mail Critical No bounty
  • nextcloud/nextcloud_announcements Critical No bounty
  • nextcloud/notes Critical No bounty
  • nextcloud/notifications Critical No bounty
  • nextcloud/notify_push Critical No bounty
  • nextcloud/password_policy Critical No bounty
  • nextcloud/photos Critical No bounty
  • nextcloud/preferred_providers Critical No bounty
  • nextcloud/privacy Critical No bounty
  • nextcloud/recommendations Critical No bounty
  • nextcloud/related_resources Critical No bounty
  • nextcloud/richdocuments Critical No bounty
  • nextcloud/server Critical No bounty
  • nextcloud/serverinfo Critical No bounty
  • nextcloud/sharepoint Critical No bounty
  • nextcloud/socialsharing Critical No bounty
  • nextcloud/spreed Critical No bounty
  • nextcloud/survey_client Critical No bounty
  • nextcloud/suspicious_login Critical No bounty
  • nextcloud/terms_of_service Critical No bounty
  • nextcloud/text Critical No bounty
  • nextcloud/twofactor_totp Critical No bounty
  • nextcloud/twofactor_webauthn Critical No bounty
  • nextcloud/updater Critical No bounty
  • nextcloud/user_migration Critical No bounty
  • nextcloud/user_oidc Critical No bounty
  • nextcloud/user_saml Critical No bounty
  • nextcloud/viewer Critical No bounty
  • nextcloud/workflow_script Critical No bounty

Web 24

  • apps.nextcloud.com Critical No bounty
  • auth.nextcloud.com Critical No bounty
  • crm.nextcloud.com Critical No bounty
  • customerupdates.nextcloud.com Critical No bounty
  • docs.nextcloud.com Critical No bounty
  • download.nextcloud.com Critical No bounty
  • help.nextcloud.com Critical No bounty
  • knowledge.nextcloud.com Critical No bounty
  • lists.nextcloud.com Critical No bounty
  • logs.nextcloud.com Critical No bounty
  • lookup.nextcloud.com Critical No bounty
  • newsletter.nextcloud.com Low No bounty
  • nextcloud.com Critical No bounty
  • portal.nextcloud.com Critical No bounty
  • projects.nextcloud.com Critical No bounty
  • pushfeed.nextcloud.com Low No bounty
  • push-notifications.nextcloud.com Critical No bounty
  • scan.nextcloud.com Critical No bounty
  • static.apps.nextcloud.com Critical No bounty
  • stats.nextcloud.com Critical No bounty
  • support.nextcloud.com Critical No bounty
  • surveyserver.nextcloud.com Critical No bounty
  • updates.nextcloud.com Critical No bounty
  • usercontent.apps.nextcloud.com Critical No bounty

Android apps 3

  • com.nextcloud.client Medium No bounty
  • com.nextcloud.talk2 Medium No bounty
  • it.niedermann.owncloud.notes Medium No bounty

iOS apps 3

  • com.nextcloud.Talk Medium No bounty
  • com.peterandlinda.iOCNotes Critical No bounty
  • it.twsweb.Nextcloud Medium No bounty

Desktop and binaries 1

  • Desktop Client Critical No bounty
Out of scope (8)
  • daita/files_fulltextsearch_tesseract
  • cloud.nextcloud.com
  • conf.nextcloud.com
  • demo.nextcloud.com
  • drone.nextcloud.com
  • https://nextcloud.atlassian.net/jira/dashboard
  • sentry.nextcloud.com
  • try.nextcloud.com

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Nextcloud (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • We accept only issues that you have reproduced yourself, proven by screenshots.
  • Do not submit a report before reproducing the issue.
  • DO NOT include Personally Identifiable Information (PII) in your report
  • If you use large language models (LLMs), please disclose how you used LLMs
  • Please do not run any Denial of Service attacks against our infrastructure or extract user data.
  • Please do also refrain from using automated testing tools against our infrastructure.
  • Do not disclose bugs to other parties before we have published a patch.

Not accepted

  • Missing X-Frame-Options on the download servers
  • Denial of Service

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-45691 Medium 5.9 1 Jun 2026
CVE-2026-45810 Medium 6.8 1 Jun 2026
CVE-2026-45722 High 7.1 1 Jun 2026
CVE-2026-45690 Medium 5.9 1 Jun 2026
CVE-2026-45544 Medium 4.3 1 Jun 2026
CVE-2026-45545 High 8.2 1 Jun 2026
CVE-2026-45543 Medium 5.3 1 Jun 2026
CVE-2026-45284 Medium 4.6 1 Jun 2026
CVE-2026-45286 Medium 4.3 1 Jun 2026
CVE-2026-45285 Medium 6.4 1 Jun 2026
CVE-2026-45283 Medium 6.3 1 Jun 2026
CVE-2026-45279 Medium 4.4 1 Jun 2026
CVE-2026-45282 Medium 6.5 1 Jun 2026
CVE-2026-45281 High 8.1 1 Jun 2026
CVE-2026-45278 Low 3.3 1 Jun 2026
CVE-2026-45277 Low 3.3 1 Jun 2026
CVE-2026-45275 Medium 6.5 1 Jun 2026
CVE-2026-22683 High 8.7 7 Apr 2026
CVE-2025-64011 Medium 4.3 12 Dec 2025
CVE-2025-66554 Low 3.5 5 Dec 2025
CVE-2025-66558 Low 3.1 5 Dec 2025
CVE-2025-66557 Medium 5.4 5 Dec 2025
CVE-2025-66556 Low 3.5 5 Dec 2025
CVE-2025-66548 Low 3.3 5 Dec 2025
CVE-2025-66553 Medium 4.3 5 Dec 2025
CVE-2025-66551 Medium 6.3 5 Dec 2025
CVE-2025-66515 Low 2.7 5 Dec 2025
CVE-2025-66549 Low 2.4 5 Dec 2025
CVE-2025-66545 Low 3.5 5 Dec 2025
CVE-2025-66514 Low 3.5 5 Dec 2025
CVE-2025-66513 Medium 4.3 5 Dec 2025
CVE-2025-66552 Medium 4.3 5 Dec 2025
CVE-2025-66550 Medium 5.7 5 Dec 2025
CVE-2025-66546 Low 3.3 5 Dec 2025
CVE-2025-66512 Medium 5.4 5 Dec 2025
CVE-2025-66511 Medium 4.8 5 Dec 2025
CVE-2025-66510 Medium 4.5 5 Dec 2025
CVE-2025-66547 Medium 4.3 5 Dec 2025
CVE-2025-59788 Medium 6.4 4 Dec 2025
CVE-2025-47791 Medium 4.3 16 May 2025
CVE-2025-47794 Low 2.6 16 May 2025
CVE-2025-47793 Medium 4.3 16 May 2025
CVE-2025-47792 Medium 5.0 16 May 2025
CVE-2025-47790 Medium 6.4 16 May 2025
CVE-2024-52512 Low 3.3 15 Nov 2024
CVE-2024-52514 Medium 4.1 15 Nov 2024
CVE-2024-52513 Low 2.6 15 Nov 2024
CVE-2024-52511 Medium 6.3 15 Nov 2024
CVE-2024-52508 High 8.2 15 Nov 2024
CVE-2024-52510 Medium 4.2 15 Nov 2024
CVE-2024-52509 Low 3.5 15 Nov 2024
CVE-2024-52507 Low 3.5 15 Nov 2024
CVE-2024-52523 Medium 4.6 15 Nov 2024
CVE-2024-52525 Low 1.8 15 Nov 2024
CVE-2024-52521 Low 2.6 15 Nov 2024
CVE-2024-52519 Low 2.7 15 Nov 2024
CVE-2024-52520 Medium 5.7 15 Nov 2024
CVE-2024-52518 Medium 4.4 15 Nov 2024
CVE-2024-52517 Medium 4.6 15 Nov 2024
CVE-2024-52516 Low 3.0 15 Nov 2024

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

We're inviting researchers all over the globe to take a look at Nextcloud and bring its security to the next level. If you're interested in learning how we handle security you can read more about it on our dedicated security page.

Important notice ⚠️

No monetary bounties

Please note that Nextcloud does not offer monetary bounties for security reports submitted through this program.

Due to the large amount of AI-generated illegitimate reports, we have temporarily suspended our paid bounty program and no financial rewards will be awarded for any submissions, regardless of severity. We remain deeply committed to security and to working with the research community. Valid reports will still be triaged, fixed, and publicly acknowledged after disclosure, and reporters will continue to receive recognition through this platform. We greatly appreciate the time and effort that researchers invest in helping us keep Nextcloud secure.

As you are likely aware, this is an industry-wide challenge and like others, we have been unable to find ways to responsibly handle the massive increase of low quality reports. We hope to be able to restart the program once a reliable approach to filtering out the low-effort reports has been found. We have already engaged with HackerOne on this and will continue to do so.

AI-generated reports

Given the high number of generic AI security reports, we are emphasizing the following:

  • We accept only issues that you have reproduced yourself, proven by screenshots.
  • Do not submit a report before reproducing the issue.

Low-effort AI-generated reports will be ignored and closed as Spam (-10 reputation) and may lead to your suspension from this program.

Program policy

  • Keep your reports short and concise, only include the relevant information about what the threat is and how to reproduce it. Do not overexaggerate your reports.
  • DO NOT include Personally Identifiable Information (PII) in your report and please REDACT/OBFUSCATE the PII that is part of your PoC (screenshot, server response, JSON file, etc.) as much as possible.
  • Same rule apply to with secrets, keys and credentials.
  • If you use large language models (LLMs), please disclose how you used LLMs, and carefully review and edit its output before you send it to us. Please double-check that your reproduction steps actually work and that all the information you include in the report is valid and correct.
  • Don't leak the contents of your report up front to any SaaS solutions, such as AI services like ChatGPT, search engines, browser plugins, or translation engines. If you use services, such as large language models, only use services that run locally on your own hardware to ensure our security information does not leak to the outside world.
  • All reports must be validated manually, submission from automated tools (code analysis tools, AI, …) won't be considered unless manually reviewed and validated from your side.
  • If your report mostly contains "AI slop reports" (in other words reports that are generated largely by LLMs) or is auto generated, without careful review from you and thus result in additional work on our side or even invalid reports, we consider the following actions a valid option:
    • 🔒 Closing your reports as Spam
    • ⛔ Block you from our program

Instead of bothering you with a huge list of exclusions we're going to tell you what we're especially looking after:

  • Bugs within Nextcloud server and apps supported by Nextcloud GmbH (Note: see Scope list for all qualifying and packaged components. Third-party apps from the AppStore are not part of our program.)
    • Please check the top of our wiki for Current version to see which Nextcloud Server versions are eligible: https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule
    • For Apps only the latest version compatible with those Nextcloud Server versions are eligible
    • Reports that do not mention a Nextcloud Server version or the App version where applicable will be closed as N/A"
  • Bugs within the mobile iOS and Android sync clients
    • Only the latest version of each client available in the respective store is eligible
  • Bugs within the desktop clients for Mac, Windows, and Linux
    • Only the latest version of each client is eligible

For us a bug is something that actively allows an attacker to escalate their privileges. Something like "Attacker can delete arbitrary files of other users" is fine to be reported, "Missing X-Frame-Options on the download servers" not so much. At the moment we are also considering "Denial of Service" out of scope, we will acknowledge you though!

Found a security bug in one of the mentioned scopes? Awesome! Just report it here and we will get back to you. Bonus points if you check back with our threat model before.

Found a bug in one of our websites or app that is not in scope? We will acknowledge the issue and happily accept reports for it via this platform as well.

  • Please do not run any Denial of Service attacks against our infrastructure or extract user data.
  • Please do also refrain from using automated testing tools against our infrastructure.
  • Do not disclose bugs to other parties before we have published a patch.

We believe in transparency about our security, so any valid vulnerabilities discovered are always publicly disclosed after a grace period.

Disclosure guideline

We are committed to resolving reported vulnerabilities promptly. Our target is to provide a resolution within 90 days of triage. We ask reporters not to disclose any details about the vulnerability until a fix has been released or the 90-day resolution window has elapsed. All communication regarding the vulnerability, including status updates, clarifications, and disclosure requests should happen within the HackerOne platform. Please do not reach out through other public or private channels.

Recognition

While we no longer offer monetary rewards, we recognize the contributions of security researchers in the following ways:

  • Public acknowledgment on the HackerOne platform
  • Reputation points for valid reports
  • Credit in our security advisories upon disclosure (where applicable and with your consent)

Thank you for helping us keep Nextcloud and its users secure.