CVE-2026-112180: MISP Incomplete Event Deletion Leaves Orphaned Sensitive Records
MISP contains a data integrity flaw in its event deletion logic. When a user deletes an event, several associated records are not removed from the database, leaving them as orphaned entries. The affected record types include event report tags, event graph entries, proposal (shadow attribute) correlations, fuzzy ssdeep correlation chunks, and attachment scan results.
These orphaned records may contain sensitive threat intelligence data such as correlation mappings, scan results, and report metadata that should have been removed along with the parent event. Their persistence beyond the intended deletion lifecycle creates a risk of unintended data retention and potential information exposure if the records are reachable through other application queries or administrative interfaces.
Preconditions:
- An authenticated user with sufficient privileges to delete events in MISP.
- The event must have associated reports, graphs, correlations, ssdeep chunks, or attachment scan results.
Impact:
- Residual sensitive data persists in the database after the parent event is deleted.
- Accumulation of orphaned records over time may contribute to storage bloat.
- Orphaned records may be inadvertently exposed through other data-access paths that do not validate the existence of the parent event.
Affected versions: <2.5.48
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MISPto a version that resolves this vulnerability.Fixed in 2.5.48
Event History
Frequently Asked Questions
Who can trigger the condition?
An authenticated MISP user needs sufficient privileges to delete events. The event must also have associated reports, graphs, correlations, ssdeep chunks, or attachment scan results.
What data can remain after an event is deleted?
Affected orphaned records include event report tags, event graph entries, proposal (shadow attribute) correlations, fuzzy ssdeep correlation chunks, and attachment scan results. These may retain correlation mappings, scan results, and report metadata.
How can an organization determine whether it may be affected?
Review the database for records in the listed associated-data categories whose parent event has been deleted or no longer exists. Events deleted while containing the specified associated data are the relevant candidates for residual records.
What are the operational consequences of leaving the records in place?
Residual sensitive threat-intelligence data can persist beyond its intended deletion lifecycle and may be exposed if reachable through other application queries or administrative interfaces. Orphaned records can also accumulate over time and contribute to storage bloat.