CVE-2026-107278: MISP Object Sync Drops Objects and Attributes When Description Is Empty

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 29 Oct 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.3%

EPSS score, percentile 16.5 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

5.3 Medium

CVSS v4.0 base score, given by the CNA

What should I do?

The overly strict validation rule that required a non-empty description on MISP Objects during creation was relaxed to permit an empty description. Full textSolution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (1)

Which versions are affected?

Affected

• before 2.5.48

Versions by product

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026; CVE List, as of 29 Oct 2026. About the data.

What to do

Solution (from the CVE record)

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.

Advisories and patches

• Security patch (Patch)

This summary is based on the CVE record as of 29 Oct 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

Source: CVE List, as of 29 Oct 2026. About the data.

About this vulnerability

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…

Summary: CVE record, as of 29 Oct 2026.

• CISA has not added CVE-2026-107278 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
• The CVE record was published on 7 Oct 2026.
• The CVE record carries a CVSS v4.0 base score of 5.3 (Medium), given by its CNA.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.3% (percentile 16.5), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
• CISA's SSVC assessment in the CVE record: exploitation none, automatable no, technical impact partial.
• The credits in the CVE record name Anthropic (Claude) as finder.

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; CVE List, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026. About the data.

Description

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.

Source: CVE List, as of 29 Oct 2026. About the data.

Timeline