CVE-2026-107278: MISP Contains a Validation Flaw
Affects MISPSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.5.48 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.48
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade misp/MISP to 2.5.48.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmisp/MISPpkg:github/misp/MISPOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, ensure that all created MISP objects include a description to avoid silent data loss during synchronization.
Description
MISP has a validation flaw in its object synchronization logic where objects created without a description are rejected by receiving instances during synchronization. This causes the receiving instance to silently drop the object and its attributes, resulting in loss of threat-intelligence data. The issue occurs when multiple MISP instances synchronize and an authorized user creates an object without a description. It is not exploitable externally but can cause unintended data loss within the sync topology. The affected versions are those prior to 2.5.48.