Description
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.
Published: 2026-10-07
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Loss of threat‑intelligence data due to silent deletion of objects and attributes during synchronization
Action: Patch immediately
AI Analysis

Impact

MISP’s object‑synchronization component enforces a validation rule that rejects objects with an empty description. When an object legitimately created without a description is replicated to a peer instance, the receiving instance discards the object and all its attributes. The result is a silent loss of threat‑intelligence records, compromising the integrity of the shared data set. The flaw does not allow external exploitation; it is triggered only when an authorized user creates an object without a description and that object is subsequently synchronized.

Affected Systems

The affected product is MISP. The vulnerability exists in installations with a version older than 2.5.48. Users running any pre‑2.5.48 release of MISP should consider applying the listed fix.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity and the EPSS score is not available, implying no known widespread exploitation. The vulnerability is not in the CISA KEV catalog. Because the flaw requires an authorized user to create an object with an empty description and a synchronized peer, the risk is limited to environments where such configurations exist. The likely attack vector is an internal action by a user who creates objects without descriptions; no external attacker can trigger the defect without legitimate privileges.

Generated by OpenCVE AI on October 7, 2026 at 18:24 UTC.

Remediation

Vendor Solution

The overly strict validation rule that required a non-empty description on MISP Objects during creation was relaxed to permit an empty description. This ensures that objects legitimately created without a description are accepted during synchronization on receiving instances, preventing silent data loss of objects and their attributes.


OpenCVE Recommended Actions

  • Upgrade the MISP instance to version 2.5.48 or later to relax the description validation rule and prevent silent data loss
  • After upgrading, re‑sync existing objects from the source instance to ensure any previously dropped objects are restored
  • Adjust user guidelines to require a non‑empty description when creating MISP objects, and audit sync logs for any discarded objects

Generated by OpenCVE AI on October 7, 2026 at 18:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 07 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 07 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
Description 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.
Title MISP Object Sync Drops Objects and Attributes When Description Is Empty
First Time appeared Misp
Misp misp
Weaknesses CWE-20
CPEs cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*
Vendors & Products Misp
Misp misp
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-10-07T20:28:50.215Z

Reserved: 2026-10-07T15:42:40.660Z

Link: CVE-2026-107278

cve-icon Vulnrichment

Updated: 2026-10-07T20:28:46.128Z

cve-icon NVD

Status : Deferred

Published: 2026-10-07T16:17:47.393

Modified: 2026-10-07T21:17:15.030

Link: CVE-2026-107278

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-08T00:00:14Z

Weaknesses
  • CWE-20

    Improper Input Validation