CVE-2026-94374

8.3

MISP · MISP

MISP is vulnerable to an insecure direct object reference in the Event model, allowing authenticated users to read or modify arbitrary event reports by manipulating the report ID field.

Executive summary

An authorization bypass vulnerability in MISP allows authenticated users to read or modify unauthorized event reports, posing a significant risk to data integrity and confidentiality.

Vulnerability

This vulnerability is an insecure direct object reference (CWE-639) located in the processModuleResultsData method of the Event model. An authenticated user with permissions to submit module results can inject an existing report ID into their request, causing the application to overwrite or disclose sensitive data from other events.

Business impact

The ability to overwrite or reassign ownership of event reports could lead to the corruption of threat intelligence data and the unauthorized disclosure of sensitive security incidents. With a CVSS score of 8.3, this flaw represents a high-severity risk to organizational security operations, as it compromises the core integrity of the threat intelligence platform.

Remediation

Immediate Action: Upgrade MISP to version 2.5.47 or later to implement the necessary input validation that strips client-supplied ID fields during report processing.

Proactive Monitoring: Review application logs for unusual module result submissions and monitor EventReport audit logs for unexpected changes to report ownership or content.

Compensating Controls: Restrict permissions for executing module result processing to a minimal set of trusted users until the software can be patched.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the potential for unauthorized modification of critical threat intelligence, organizations should prioritize updating to version 2.5.47 immediately. Failure to address this vulnerability allows malicious actors or compromised accounts to manipulate historical and ongoing security data, which could blind security teams or lead to the exposure of sensitive incident information.

More MISP CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Jeroen Pinoy, with iglocska (remediation developer), Claude Opus 4.8 (remediation developer), per the CVE Program record.