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

> Authorized users can cause silent data loss during synchronization by creating objects without descriptions, compromising threat intelligence integrity.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-3fqm-jh2r-j26f

## What is CVE-2026-107278?

CVE-2026-107278 is a medium-severity vulnerability in MISP, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-107278?


## How do I fix CVE-2026-107278?

No fix has been published for CVE-2026-107278 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107278 being exploited?

There is no known exploitation of CVE-2026-107278 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107278 and fix it if it is affected.

What it is: CVE-2026-107278 is a medium-severity vulnerability in MISP, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107278 in the wild and no public exploit code.

Affected product: MISP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107278/ (Markdown: https://insights.sbomify.com/CVE-2026-107278/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107278
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107278
- OSV: https://osv.dev/vulnerability/CVE-2026-107278

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107278/
Summaries are generated and may contain mistakes; the official description above is the record.
