CVE-2026-133175
What it is
MISP 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-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. 2. 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.
At a glance
- Exploitability
- Can be exploited over the network with an admin-level account. High risk of data tampering.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: 6.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Weakness
- CWE-862 · Missing authorization
- Record status
- Received
Affected
- Misp ≤ 2.5.51
Attack profile CVSS 4.0 · 6.9
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- None
- Privileges needed
- High
- User interaction
- None
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-133175.md and follow it. Check whether this project is affected by CVE-2026-133175. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.