CVE-2026-107278: MISP Object Sync Drops Objects and Attributes When Description Is Empty
MISP contains a validation flaw in its object synchronization logic. When a MISP Object is created without a description, it is stored correctly on the originating instance. However, when that object is replicated to another MISP instance via the sync mechanism, the receiving instance's validation rule rejects the object because the description field is empty. As a result, the receiving instance silently drops the object along with all of its associated attributes, leading to loss of threat-intelligence data.
Preconditions:
- Two or more MISP instances are configured to synchronize objects.
- A user with object-creation privileges creates an object without supplying a description.
- The object is subsequently synced to a peer instance.
Impact:
- Valid objects and their attributes are silently discarded on receiving instances, causing data-integrity loss in the threat-intelligence pipeline.
- The issue is not externally exploitable in a traditional sense but can be triggered by any authorized user who creates objects without descriptions, resulting in unintended data loss across the sync topology.
Affected: <2.5.48.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MISPto a version that resolves this vulnerability.Fixed in 2.5.48
Event History
Frequently Asked Questions
Which deployments are exposed to data loss?
Deployments with two or more MISP instances configured to synchronize objects are exposed when they run an affected version below 2.5.48. The originating instance retains the object, but receiving peers can discard it and its associated attributes.
What access is required to trigger the issue?
An authorized user needs object-creation privileges and must create an object without a description. The object must then be synchronized to a peer MISP instance.
What can be done before updating?
Require users creating MISP Objects to supply a description before the object is synchronized. This avoids the empty-description validation failure on receiving instances.