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.
Analysis and contextual insights are available on OpenCVE Cloud.
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.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://github.com/MISP/MISP/commit/e4fa73719 |
|
Thu, 19 Nov 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MISP: External Sync User Can Modify Protected Events Without Signature via Multiple Write Routes | |
| First Time appeared |
Misp
Misp misp |
|
| Weaknesses | CWE-285 CWE-862 |
|
| CPEs | cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Misp
Misp misp |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-19T14:25:18.823Z
Reserved: 2026-11-19T13:55:10.863Z
Link: CVE-2026-133163
No data.
Status : Deferred
Published: 2026-11-19T14:17:29.263
Modified: 2026-11-19T14:17:29.380
Link: CVE-2026-133163
No data.
OpenCVE Enrichment
No data.