CVE-2026-88915
moderateMissing Authorization Checks in MISP Event Template Instantiation
MISP versions up to and including 2.5.45 do not consistently enforce the acting user's authorization when instantiating event templates (CWE-862, missing authorization). An authenticated user who instantiates a template can cause an event to be created with a sharing group (distribution = 4) that the user is not actually permitted to use, because the template-supplied sharing_group_id is written directly into event creation without a SharingGroup::canUse() check. The same path also attaches template-specified tags without checking the user's tagging permissions and hardcodes local => 0, so tags marked local_only are attached globally and can propagate to other instances through synchronization or export, contrary to their intended restriction. An attacker gains unauthorized write access to event metadata (sharing-group assignments and tags), an integrity issue in shared threat intelligence rather than a confidentiality or availability problem. All MISP deployments running version 2.5.45 or earlier are affected; no public proof-of-concept is known and the flaw is not in CISA's Known Exploited Vulnerabilities catalog.
What to do: Upgrade MISP to any release later than 2.5.45, which adds SharingGroup::canUse() authorization for the acting user, applies normal tag-modification permission checks during template instantiation, and attaches local_only tags locally. Until patched, review events created via template instantiation for sharing-group assignments or globally attached tags that the creating users were not entitled to set, and check whether local_only tags have propagated to downstream instances via synchronization or export. Consider restricting which users may instantiate event templates as an interim mitigation.
| MISP Project MISP | <= 2.5.45 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Affected versions of MISP do not consistently enforce the acting user's authorization when instantiating event templates. For templates using distribution = 4, the template can specify a sharing_group_id. The instantiation path passed that value into event creation without verifying that the user instantiating the template was actually permitted to use the selected sharing group. The commit notes that Event::_add() only performed its own sharing-group authorization in another code path, leaving template instantiation able to write the identifier directly. The same instantiation path also attached template-specified tags without checking the user's normal tagging permissions. In addition, it hardcoded local => 0, meaning tags marked local_only could be attached globally and consequently propagate through synchronization or export, contrary to their intended restriction. The fix adds explicit SharingGroup::canUse() authorization for the acting user, applies the same tag-modification checks used by normal event tagging, and ensures local_only tags are attached locally. Version affected: ≤2.5.45
- Weakness
- CWE-862
- Vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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:X
In the news0 stories
No ingested article mentions this CVE yet.