CVE-2026-94374: MISP: IDOR via Client-Supplied Report ID in Module Results Processing Allows Reparenting and Overwriting of Other Events' Reports

Published Sep 21, 2026
·
Updated

MISP contains an insecure direct object reference vulnerability in the processModuleResultsData method of the Event model. When processing module results, the code iterates over EventReport entries supplied in the resolved data and saves each one. Unlike the adjacent attribute and object processing loops, the report loop did not unset the client-supplied 'id' field before calling save(). Because the MISP EventReport model's create() method does not strip the id field, an authenticated user with permission to submit module results could include an 'id' value referencing an existing report belonging to a different event. Upon save(), the ORM would update that existing row rather than insert a new one, allowing the attacker to

- read the content of another event's report by reparenting it into their own event  - overwrite the report's fields with attacker-controlled data  - change the report's eventid to redirect ownership.

This constitutes an authorization bypass through a user-controlled key, enabling cross-event data disclosure and integrity compromise. The vulnerability requires an authenticated session with the ability to invoke module result processing on an event.

Version affected: <2.5.47

Affected Software

1 affected component
Misp Misp<2.5.47

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in <2.5.47

Event History

Sep 21, 2026
CVE Published
via MITRE·12:25 PM
Data Sourced
via MITRE·12:25 PM
RemedyDescriptionWeakness

Frequently Asked Questions

1

Does any authenticated MISP user have the access needed to exploit this issue?

No. Exploitation requires an authenticated session and permission to invoke module result processing on an event.

2

Can the issue affect reports associated with events other than the attacker's own event?

Yes. An attacker who can submit module results can supply the ID of an existing report from another event, causing it to be reparented to the attacker's event. This can expose its contents, overwrite its fields, and redirect its event ownership.

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