Medium · CVSS 5.1CVE-2026-112180

MISP Incomplete Event Deletion Leaves Orphaned Sensitive RecordsCVE-2026-112180

Answer in brief

CVE-2026-112180 records a Medium severity (CVSS 5.1) vulnerability in MISP Incomplete Event Deletion Leaves Orphaned Sensitive Records. The current sources do not mark it as known exploited. The current feed maps MISP/MISP (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 19, 2026Updated Oct 19, 2026Source checked Oct 19, 2026First seen by HOL Oct 19, 2026Material review Oct 19, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 5.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps MISP/MISP (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
MISP/MISPgeneric	>=0 <=2.5.48	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for MISP/MISP.
Review the reported fix. Source-reported solution: The event deletion routine was extended to cascade-remove all associated child records that were previously left behind. Specifically, the fix ensures that event report tags, event graph rows, shadow attribute correlation rows (on both event_id and 1_event_id foreign keys), fuzzy ssdeep chunks, and attachment scan results are all purged within the same transaction as the parent event deletion, eliminating the orphaned-data condition.

Evidence timeline and material changes

Published upstream
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 19, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source 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

Quoted source text, attributed separately from HOL analysis.