CVE-2026-103858: MISP Incomplete Thread Authorization Allows Unauthorized Read and Post Access to Discussions

Published Oct 1, 2026
·
Updated

MISP contains an incomplete authorization check in the discussion posting functionality. When a user submits a post to a thread or replies to an existing post, the application only verified whether the target thread was restricted to a single organization (org-only distribution). It did not enforce the full thread access control list, including sharing-group membership and event-level visibility.

As a result, an authenticated user who is outside the relevant sharing group or who does not have visibility on the associated event could:

- Read the thread title and the content of the quoted post

- Submit a new post into the discussion thread

This constitutes both an information disclosure (reading restricted thread and post content) and an integrity issue (injecting content into a thread the user is not authorized to participate in).

Affected: <2.5.48

Affected Software

1 affected component
Misp Misp<2.5.48

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade MISP to a version that resolves this vulnerability.

    Fixed in 2.5.48

Event History

Oct 1, 2026
CVE Published
via MITRE·11:31 AM
Data Sourced
via MITRE·11:31 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which users can exploit this issue?

An authenticated MISP user can exploit it if they can target a discussion thread but are not a member of the relevant sharing group or do not have visibility of the associated event. The issue applies where access is restricted through sharing-group membership or event-level visibility rather than only an org-only thread restriction.

2

What information and actions are exposed through a successful exploit?

An unauthorized user can read the discussion thread title and the content of a quoted post. They can also submit a new post or reply to the restricted discussion thread.

3

Are versions prior to the fixed release affected?

MISP versions earlier than 2.5.48 are affected. The provided data does not identify any other affected version ranges or configuration prerequisites.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203