CVE-2026-132644 json
MISP Galaxy Cluster Import Authorization Bypass Allows Cross-Organization Cluster Takeover
published 3h ago modified 2h ago also EUVD-2026-129227
- cvss
- 6.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
MISP contains an authorization flaw in the GalaxyCluster model's captureCluster() function, which handles the import and synchronization of Galaxy Clusters. Prior to the fix, any authenticated user holding the galaxy editor role could replace an existing locked Galaxy Cluster by supplying its UUID in an import request, regardless of which organization owned the cluster. The function unconditionally called captureOrganisationAndSG() before the save operation, overwriting the cluster's org_id and orgc_id fields with the importing user's organization, effectively transferring ownership of the cluster to the attacker's organization. Additionally, the save operation was not restricted to a specific set of fields, allowing arbitrary field modification.
The vulnerable behavior required the attacker to possess a valid MISP account with the perm_galaxy_editor role and to know or discover the UUID of a target cluster belonging to another organization. No site-admin or owner-organization privilege was enforced for the update path. The result was that a low-privilege galaxy editor in one organization could modify the content (value, description, distribution, etc.) of clusters owned by other organizations and seize ownership, corrupting the integrity of shared threat-intelligence data across the MISP instance.
The vulnerability was reported by ENISA and CERT.pl. The fix introduces an explicit authorization gate that restricts cluster updates to the owner organization, a sync user who can see the cluster via sharing-group rules, or a site administrator, and enforces a field allow-list that excludes org_id and orgc_id from update writes, preserving original ownership.
Patch / fix
- github.com/MISP/MISP@4ac836a commit
Is CVE-2026-132644 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:H/SA:N |
Affected products
- misp misp
Classification
References
Sources
- CVE List CVE-2026-132644
- NVD CVE-2026-132644
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.