Skip to content
Threat Brief

← All advisories

CVE-2026-133163

Medium 5.3No known exploitationFix available

MISP: External Sync User Can Modify Protected Events Without Signature via Multiple Write Routes

Record last updated

CVSS score

5.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 22% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

MISP contains an authorization bypass affecting the event protection mechanism. In MISP, a protected event is designed to be modifiable only through the events/edit endpoint with a valid cryptographic signature. However, the protection check was enforced solely on that single route. All other write endpoints that operate on an event—attributes (add, edit, delete), objects (delete), events (populate, publish, unprotect, upload_sample, upload_analysis_file), tags (attach, detach), event reports (edit, delete), galaxy clusters (attach, detach), and cryptographic keys (add, delete)—lacked the equivalent check. As a result, an authenticated user holding the sync permission (perm_sync) who is neither a site administrator nor an internal sync user (perm_sync_internal), and who belongs to the same organization as the event's creator (orgc_id), could modify, delete, or add data to a protected event without providing a valid signature. This included the ability to unprotect the event entirely, publish it to other instances, and add cryptographic signing keys that would subsequently permit signed edits, effectively nullifying the protection mechanism. The vulnerability requires an authenticated sync user account within the event's creator organization. No user interaction or special network conditions are required; standard API calls to the affected endpoints are sufficient. The security impact is a loss of integrity over protected threat-intelligence events: an attacker can inject, alter, or remove attributes, objects, tags, reports, and galaxy cluster associations, and can remove the protection flag or add signing keys to enable persistent unauthorized modification.

Weakness: CWE-862, CWE-285

Patching and mitigation

Patch status
Fix available (source: CVE record (CIRCL))
Fix documented (source date)
Vendor solution
A shared authorization check (isProtectedFromSyncUser / assertNotProtectedFromSyncUser) was introduced in the Event model and enforced across all write paths. The check denies any non-internal, non-site-admin sync user from modifying a protected event through any route other than events/edit with a valid signature. The check is now invoked in the ACL component (modify, publish, tag), in the CryptographicKeys, Events, and Tags controllers, and in the Event, EventReport, Galaxy, and MispAttribute models, closing every previously unprotected write path.
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
mispmispall versions up to and including 2.5.51Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by CIRCL

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (CIRCL)

    Source: CVE record (CIRCL) (opens in a new tab)

Vendor guidance and references