Description
Affected versions of MISP allow a collection element to be created from a bare UUID without consistently checking whether the acting user is allowed to access the referenced object.


The commit explains that collection elements themselves only store UUIDs, while the collection view later resolves those UUIDs into their underlying objects. Before this fix, the generic add() path could therefore persist a UUID for an Event or Galaxy Cluster that the caller could not normally read. The patch explicitly notes that this made collections a way to reference another organisation’s private data and had caused disclosure of organisation-only events in the beta collection view.


The fix centralizes authorization in __assertCanUseElements(). Event UUIDs are validated through Event::fetchSimpleEvent() under the current user’s ACL, while Galaxy Cluster UUIDs are checked through GalaxyCluster::fetchGalaxyClusters(). The check is applied both to the CRUD add() path and to addElementToCollection().

Version affected: ≤2.5.45
Published: 2026-09-15
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized disclosure of private MISP events or galaxy clusters
Action: Immediate Patch
AI Analysis

Impact

A vulnerability in MISP allows an attacker to create a collection element that references an event or galaxy cluster by its UUID without verifying that the user has permission to read that object. The missing authorization gate lets a malicious actor persist a UUID pointing to another organisation’s private data. Once the collection is viewed, the referenced object is resolved and can be exposed to users who should not have access, leading to confidentiality leakage of sensitive MISP content.

Affected Systems

The issue affects all MISP installations using a version 2.5.45 or earlier. Administrators should verify that the product is upgraded beyond this release or apply the upstream commit that introduces the __assertCanUseElements() guard in the add() CRUD path and addElementToCollection() method.

Risk and Exploitability

The vulnerability carries a CVSS score of 7.1, indicating high severity, but its EPSS value is below 1% and the flaw is not listed in the CISA KEV catalogue, so the current probability of exploitation is low. Attackers could exploit the flaw by crafting an API or web request that submits a bare UUID to the collection add endpoint. If successful, the system will silently store the reference, and later legitimate list or view operations will resolve the UUID and expose the underlying object to unauthorised viewers. Because the flaw operates before authorization checks, it bypasses normal ACL controls and can be used to leak private data to any party who can add collection elements.

Generated by OpenCVE AI on September 16, 2026 at 06:05 UTC.

Remediation

Vendor Solution

The fix introduces a dedicated __assertCanUseElements() authorization guard that is invoked in the beforeSave callback of the add() CRUD path (covering both form and REST submission) and in addElementToCollection(). For each element UUID, the method resolves the element type (deducing it if the caller omitted the field, preventing bypass by omission) and performs an ACL-aware lookup: for Events it calls fetchSimpleEvent() scoped to the current user, and for GalaxyClusters it calls fetchGalaxyClusters() with the user context. If the object does not exist or the caller lacks access, a NotFoundException is raised and the save is aborted. This ensures that no collection element can reference an object the caller is not authorized to read.


OpenCVE Recommended Actions

  • Upgrade MISP to a version newer than 2.5.45, or apply the patch from commit 334d53709 that introduces the __assertCanUseElements() authorization guard.
  • Verify that the collection add API and form submit paths now call __assertCanUseElements() and that unauthorized collection elements are rejected with a NotFoundException.
  • Restrict the ability to add collection elements to users who have explicit permission to reference external objects, and review existing collections for potentially leaked references.

Generated by OpenCVE AI on September 16, 2026 at 06:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 15 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Tue, 15 Sep 2026 09:45:00 +0000

Type Values Removed Values Added
First Time appeared Misp
Misp misp
Vendors & Products Misp
Misp misp

Tue, 15 Sep 2026 08:45:00 +0000

Type Values Removed Values Added
Description Affected versions of MISP allow a collection element to be created from a bare UUID without consistently checking whether the acting user is allowed to access the referenced object. The commit explains that collection elements themselves only store UUIDs, while the collection view later resolves those UUIDs into their underlying objects. Before this fix, the generic add() path could therefore persist a UUID for an Event or Galaxy Cluster that the caller could not normally read. The patch explicitly notes that this made collections a way to reference another organisation’s private data and had caused disclosure of organisation-only events in the beta collection view. The fix centralizes authorization in __assertCanUseElements(). Event UUIDs are validated through Event::fetchSimpleEvent() under the current user’s ACL, while Galaxy Cluster UUIDs are checked through GalaxyCluster::fetchGalaxyClusters(). The check is applied both to the CRUD add() path and to addElementToCollection(). Version affected: ≤2.5.45
Title MISP Collection Element Add Missing Authorization on Referenced Object UUID
Weaknesses CWE-639
CWE-862
References
Metrics cvssV4_0

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


cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-09-15T13:50:14.847Z

Reserved: 2026-09-15T08:36:20.997Z

Link: CVE-2026-91846

cve-icon Vulnrichment

Updated: 2026-09-15T13:50:11.174Z

cve-icon NVD

Status : Received

Published: 2026-09-15T09:16:45.897

Modified: 2026-09-15T14:17:47.767

Link: CVE-2026-91846

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-16T06:15:07Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization