MISP contains an authorization flaw in the sharing group capture logic. When a sharing group is re-captured with a newer modified timestamp and an updated roster, the application unconditionally overwrote the type, nationality, sector, and contacts fields of every organisation listed in the roster, including the host organisation. This behaviour was reachable by any user holding the perm_sync role, and additionally by any external server pulled from or any feed fetched, because those operations execute with the privileges of the site administrator who initiated them. As a result, a low-privileged sync user or a malicious/compromised external feed or pull source could silently corrupt organisation records on the receiving MISP instance without any site-admin or internal-sync authorization. The vulnerability does not disclose data or affect availability; the impact is limited to integrity of organisation metadata (type, nationality, sector, contacts). The fix restricts organisation detail updates to internal sync operations (pulls over links flagged as internal, or senders holding perm_sync_internal) and site administrators; all other sync, pull, and feed operations may only match existing organisations by UUID or create new ones, without modifying their stored details.
0.4% estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-133177 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133177?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133177?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-133177 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.