CVE-2026-112180 MISP Incomplete Event Deletion Leaves Orphaned Sensitive Records
Authenticated users deleting events in MISP leave orphaned sensitive records, potentially exposing threat intelligence data through other access paths.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-112180?
CVE-2026-112180 is a medium-severity vulnerability in MISP, published on 19 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
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
Weakness: CWE-459
Which versions are affected by CVE-2026-112180?
How do I fix CVE-2026-112180?
No fix has been published for CVE-2026-112180 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-112180 being exploited?
There is no known exploitation of CVE-2026-112180 in the wild and no public exploit code.
Sources
Also known as GHSA-h2mh-3ph9-5x6g.