Skip to content

MISP

Bug bounty on Sorona misp-project.org

Accepting reports open-source
Top reward
$1,500
Top severity paid
Critical
Assets in scope
10
Public CVEs
60
Last change
No changes yet

At a glance

What to know before you start testing.

Pays from $1,500
for critical bugs.
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Sorona lists as the payout for each severity.

Severity Reward
Critical $1,500+
High $700+
Medium $300+
Low $100 $100 / 1 month Claude Max
Safe harbor
Partial Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.

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

Scope

10 assets you may test, 4 excluded.

Web 1

  • https://www.misp-project.org

Products and areas 9

  • ApacheAuthenticate and the external authentication paths, including the LDAP integration
  • Authentication and session handling end to end: local login, authentication keys and their reset flow, and the role and permission model behind both
  • CIRCL takes vulnerability reports on the MISP platform on the project's behalf, and no narrower scope is written down anywhere: the platform itself is what the channel accepts
  • File handling: attachments, malware samples, and the export formats that render stored content back out
  • Sharing groups, distribution levels and instance-to-instance synchronisation, the machinery deciding which organisation sees which event
  • The administration interface, covering user and organisation management, server settings and the diagnostics pages
  • The event, attribute, object and shadow-attribute model in full, covering creation, editing, querying and deletion across the whole data layer
  • The feed and taxonomy import paths and the other content-ingest routes, which take STIX, MISP-format and third-party intelligence authored by someone else
  • The REST API in full, along with the automation keys that scripted consumers and MISP modules authenticate with
Out of scope (4)
  • Instance misconfiguration, including sharing-group and distribution settings an administrator has set more permissively than they intended
  • Intelligence content itself: a wrong or deliberately poisoned indicator in a feed is a data-quality matter rather than a platform defect
  • MISP modules and third-party integrations, which live in their own repositories
  • The security of the peer organisations a MISP instance synchronises with, as distinct from the synchronisation code

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.

While testing

  • Submit through sorona.xyz.
  • Reporting is handled by CIRCL, the Luxembourg Computer Incident Response Center, through the contact URL published in the misp-project.org security.txt
  • Encrypt to the GnuPG key published in the project's SECURITY.md, fingerprint CA57 2205 C002 4E06 BA70 BE89 EAAD CFFC 22BD 4CD5
  • Advisories are published on misp-project.org , so coordinate any writeup with that publication rather than with a GitHub advisory
  • State the MISP version and whether the instance was synchronising with other organisations, since the sharing and feed configuration changes what an access-control finding actually reaches

Not accepted

  • a wrong or deliberately poisoned indicator in a feed is a data-quality matter rather than a platform defect
  • Instance misconfiguration, including sharing-group and distribution settings an administrator has set more permissively than they intended

Summarised with AI from the program policy on Sorona, 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-86452 High 8.7 7 Sep 2026
CVE-2026-86440 Medium 5.1 7 Sep 2026
CVE-2026-86441 Low 2.3 7 Sep 2026
CVE-2026-86451 Medium 5.3 7 Sep 2026
CVE-2026-86418 Low 2.3 7 Sep 2026
CVE-2026-86419 High 7.0 7 Sep 2026
CVE-2026-86408 High 7.1 7 Sep 2026
CVE-2026-86417 Medium 5.3 7 Sep 2026
CVE-2026-86351 Medium 5.1 7 Sep 2026
CVE-2026-86347 High 7.1 7 Sep 2026
CVE-2026-86342 Medium 5.3 7 Sep 2026
CVE-2026-85236 High 8.8 3 Sep 2026
CVE-2026-85237 High 8.6 3 Sep 2026
CVE-2026-85238 High 7.6 3 Sep 2026
CVE-2026-85239 High 7.1 3 Sep 2026
CVE-2026-85230 Medium 5.3 3 Sep 2026
CVE-2026-85216 Critical 9.5 3 Sep 2026
CVE-2026-85221 High 7.6 3 Sep 2026
CVE-2026-85226 Medium 5.3 3 Sep 2026
CVE-2026-85227 Medium 6.1 3 Sep 2026
CVE-2026-56423 Critical 9.4 22 Jun 2026
CVE-2026-56424 High 7.1 22 Jun 2026
CVE-2026-56425 Critical 9.3 22 Jun 2026
CVE-2026-56446 High 8.7 22 Jun 2026
CVE-2026-56447 Critical 9.3 22 Jun 2026
CVE-2026-10863 Medium 6.4 4 Jun 2026
CVE-2026-10864 Medium 5.3 4 Jun 2026
CVE-2026-10860 High 7.9 4 Jun 2026
CVE-2026-10854 Medium 5.3 4 Jun 2026
CVE-2026-10855 Medium 5.1 4 Jun 2026
CVE-2026-10856 Medium 5.1 4 Jun 2026
CVE-2026-10861 Medium 5.1 4 Jun 2026
CVE-2026-10611 High 8.2 2 Jun 2026
CVE-2026-9136 High 8.3 20 May 2026
CVE-2026-9137 Medium 5.1 20 May 2026
CVE-2026-44380 High 8.6 13 May 2026
CVE-2026-44381 Critical 9.3 13 May 2026
CVE-2026-44379 Medium 5.3 13 May 2026
CVE-2026-8080 Medium 6.8 7 May 2026
CVE-2026-39962 High 8.8 9 Apr 2026
CVE-2025-67906 Medium 5.4 15 Dec 2025
CVE-2024-58128 Medium 5.5 28 Mar 2025
CVE-2024-58129 Medium 5.5 28 Mar 2025
CVE-2024-58130 High 7.2 28 Mar 2025
CVE-2024-57969 Medium 4.3 14 Feb 2025
CVE-2024-46918 Medium 4.9 15 Sep 2024
CVE-2024-45509 Medium 6.5 1 Sep 2024
CVE-2024-29858 Critical 9.8 21 Mar 2024
CVE-2024-29859 Critical 9.8 21 Mar 2024
CVE-2024-25674 Critical 9.8 9 Feb 2024
CVE-2024-25675 Critical 9.8 9 Feb 2024
CVE-2023-50918 Critical 9.8 15 Dec 2023
CVE-2023-49926 Medium 6.1 3 Dec 2023
CVE-2023-48655 Critical 9.8 17 Nov 2023
CVE-2023-48656 Critical 9.8 17 Nov 2023
CVE-2023-48657 Critical 9.8 17 Nov 2023
CVE-2023-48658 Critical 9.8 17 Nov 2023
CVE-2023-48659 Critical 9.8 17 Nov 2023
CVE-2023-41098 Medium 6.1 23 Aug 2023
CVE-2023-40224 Medium 6.1 10 Aug 2023

Original policy

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

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 4 Last 12 months Injection 50 % Access control 30 % Auth bypass 15 % Latest advisories Loading the feed Overview MISP is the threat-intelligence sharing platform running at national CSIRTs, sectoral ISACs, CERTs and critical-infrastructure operators, and what sits inside an instance is the live record of who is attacking whom and which incidents are still open. It is federated by design, synchronising events with other organisations' instances under a sharing-group policy, so an access-control defect dissolves the boundary between all of them at once. CVE-2026-44381 is the reference point: a CRITICAL SQL injection through unvalidated ordering parameters, reaching the whole intelligence database in one step. CIRCL handles disclosure and there is no money attached to any of it, so sorona.xyz pays you directly on qualified, reproduced findings. In scope CIRCL takes vulnerability reports on the MISP platform on the project's behalf, and no narrower scope is written down anywhere: the platform itself is what the channel accepts The event, attribute, object and shadow-attribute model in full, covering creation, editing, querying and deletion across the whole data layer Authentication and session handling end to end: local login, authentication keys and their reset flow, and the role and permission model behind both ApacheAuthenticate and the external authentication paths, including the LDAP integration Sharing groups, distribution levels and instance-to-instance synchronisation, the machinery deciding which organisation sees which event The feed and taxonomy import paths and the other content-ingest routes, which take STIX, MISP-format and third-party intelligence authored by someone else The REST API in full, along with the automation keys that scripted consumers and MISP modules authenticate with File handling: attachments, malware samples, and the export formats that render stored content back out The administration interface, covering user and organisation management, server settings and the diagnostics pages Out of scope MISP modules and third-party integrations, which live in their own repositories Intelligence content itself: a wrong or deliberately poisoned indicator in a feed is a data-quality matter rather than a platform defect Instance misconfiguration, including sharing-group and distribution settings an administrator has set more permissively than they intended The security of the peer organisations a MISP instance synchronises with, as distinct from the synchronisation code Most-valued findings SQL injection anywhere in query construction, already the single densest class in this project's record: CVE-2026-44381 reached the entire intelligence database through unvalidated ordering parameters in the event and shadow-attribute queries Access-control defects across the sharing boundary, meaning anything that lets one organisation read events, attributes or shadow attributes another restricted, because federation is the product and that boundary is the whole of it Privilege escalation to admin or site-admin, the outcome CVE-2026-44380 reached through the auth-key reset flow Injection through external authentication, particularly the LDAP path that carried CVE-2026-39962, which sits in front of every user on the instances that use it Anything reachable through the sync or feed ingest path, since a MISP instance accepts data from peer organisations by design and one compromised peer should not become a foothold in every instance it shares with Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Reporting is handled by CIRCL, the Luxembourg Computer Incident Response Center, through the contact URL published in the misp-project.org security.txt Encrypt to the GnuPG key published in the project's SECURITY.md, fingerprint CA57 2205 C002 4E06 BA70 BE89 EAAD CFFC 22BD 4CD5 Expect a short turnaround: the project states it usually fixes confirmed vulnerabilities in less than 48 hours, so plan your disclosure window around that rather than a 90-day default Advisories are published on misp-project.org , so coordinate any writeup with that publication rather than with a GitHub advisory State the MISP version and whether the instance was synchronising with other organisations, since the sharing and feed configuration changes what an access-control finding actually reaches Disclosure Coordinated through CIRCL, the Luxembourg national CERT, which handles vulnerability reports on the project's behalf and publishes advisories on misp-project.org . The project's own commitment is unusually fast, with confirmed vulnerabilities usually fixed inside 48 hours, so the practical embargo is measured in days. Both the credit and the advisory come out of CIRCL's process rather than a repository pipeline. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability