CVE-2026-133175Medium· 6.9▾ SunlitMISP contains an authorization bypass in its server-to-server proposal synchronization mechanism. Two related flaws were identified: 1. The events/pushProposals endpoint located the target event by UUID without enforcing any access-cont…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 38 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.4%
MISP contains an authorization bypass in its server-to-server proposal synchronization mechanism. Two related flaws were identified:
The events/pushProposals endpoint located the target event by UUID without enforcing any access-control check. A sync user with perm_sync could push shadow-attribute proposals to any event on the local instance, including events with restricted distribution (e.g., distribution level 0, visible only to the owning organisation). The stored proposal also carried the sender-supplied event_uuid and event_org_id rather than the local event's actual identity, corrupting the data model.
When accepting an edit proposal (old_id != 0), the code resolved the target live attribute by UUID alone (Attribute.uuid = shadow.uuid) without scoping the lookup to the proposal's own event. A malicious sync user could therefore craft a proposal whose uuid matched an attribute in a different event; upon acceptance, the wrong attribute would be modified or deleted. The same unscoped lookup existed in the ShadowAttribute::acceptProposal path.
Preconditions: an authenticated user with sync permission (perm_sync) on a MISP instance that participates in server-to-server synchronisation. The attacker must know or enumerate the UUID of a target event or attribute.
Security impact: unauthorised read access to restricted events, unauthorised insertion of proposals onto events the user cannot see, and unauthorised modification or deletion of attributes belonging to other events. This compromises the confidentiality and integrity of threat-intelligence data across organisational boundaries within a MISP deployment.
misp <= 2.5.51The fix enforces proper authorization scoping at two levels. First, pushProposals now resolves the event through fetchSimpleEvent (which applies ACL) and the pull path uses a new __eventSyncedWithServer helper that verifies the event is actually shared with the syncing server before accepting proposals. The stored event_id, event_uuid, and event_org_id are taken from the local event record, not from sender-supplied fields. Second, a new findTargetAttribute method requires all three of Attribute.id, Attribute.event_id, and Attribute.uuid to match simultaneously, ensuring an edit proposal can only affect an attribute within its own event. Acceptance paths now reject the proposal if the target attribute cannot be resolved within the correct event scope.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-132645Medium· 6.3MISP Galaxy Import Authorization Bypass Allows Unauthorized Overwrite of Default and Other Organizations' Galaxies
CVE-2026-132644Medium· 6.3MISP Galaxy Cluster Import Authorization Bypass Allows Cross-Organization Cluster Takeover
CVE-2026-95683Medium· 5.3In MISP, the Overmind event view enriches an event with its most recent attached report for preview purposes
CVE-2026-91846High· 7.1Affected 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 themselv…
CVE-2026-133184Medium· 5.3MISP Push Mechanism Discloses Unpublished and Inaccessible Events to Remote Server
CVE-2026-133165Medium· 5.3MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass