Quick answers
- Is CVE-2026-112180 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112180 being exploited in the wild.
- How severe is CVE-2026-112180?
- Informational severity, published 19 October 2026.
- Which products and versions are affected?
- MISP Project MISP before 2.5.48.
- Is there a fix for CVE-2026-112180?
- Yes: fixed in 2.5.48. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112180 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-112180?
- Check whether you run MISP Project MISP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.5.48
Technical details
This is an incomplete deletion vulnerability in MISP's event deletion logic affecting the Event model. When an event is deleted, orphaned records are left behind in multiple tables including event_report_tags, event_graphs, proposal correlations, fuzzy ssdeep chunks, and attachment scan results. An authenticated user with sufficient privileges can delete events, and if these associated records exist, they persist in the database and may be accessible through other query paths that do not validate parent event existence.
Affected products
- MISP Project MISP before 2.5.48
Timeline
- 2026-10-19: disclosed
- 2026-10-19: patched