---
id: "CVE-2026-112180"
kind: "vulnerability"
aliases: ["CVE-2026-112180"]
title: "MISP: deleting an event leaves orphaned threat intelligence records behind"
severity: "medium"
cvss: 5.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["misp", "package", "self-hosted", "threat-intelligence"]
not_affected_if: ["version-2.5.48-or-later"]
published_at: "2026-10-19T09:17:08+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T04:29:10+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112180", "first_seen_at": "2026-10-23T21:57:17+00:00"}]
---

# MISP: deleting an event leaves orphaned threat intelligence records behind

When 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed MISP version, for example with `cat /var/www/MISP/VERSION.json` or the About page in the web UI, and compare it with `2.5.48`.
- Unknown whether the sources list specific tables or queries to inspect for orphaned rows.

## Fix

- Upgrade MISP to `2.5.48` or later.
- Unknown whether a database cleanup of existing orphaned rows is needed after upgrading; the sources do not say.

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112180

## From the sources

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

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_