Live › vulnerability › CVE-2026-112180
Go to dashboardWhen a user deletes an event in MISP, several associated records such as report tags, graph entries, correlations, ssdeep chunks and attachment scan results stay in the database. Those leftover records can hold sensitive threat intelligence data and may be reachable through other queries.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams that run MISP below version 2.5.48 and let users with event-deletion rights use it. The exposure depends on whether the leftover records can be reached through other data-access paths, which the sources do not describe in detail. Instances already on 2.5.48 or later are not affected by this flaw.
No product ranges from the sources yet.
cat /var/www/MISP/VERSION.json or the About page in the web UI, and compare it with 2.5.48.2.5.48 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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
This page as .md · .json · in your agent: get_signal("CVE-2026-112180")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.