{"id":"CVE-2026-133163","state":"PUBLISHED","title":"MISP: External Sync User Can Modify Protected Events Without Signature via Multiple Write Routes","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.\n\nAs 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.\n\nThe 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.","publishedAt":"2026-11-19T13:55:15.729Z","updatedAt":"2026-11-19T14:25:18.823Z","severity":{"score":5.3,"label":"Medium","version":"4.0","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","source":"CIRCL"},"assigner":"CIRCL","products":["misp misp"],"affected":[{"vendor":"misp","product":"misp","versions":[{"version":"0","status":"affected","lessThanOrEqual":"2.5.51","versionType":"semver"}],"cpes":["cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"],"modules":["ACLComponent","EventsController","TagsController","CryptographicKeysController","Event model","EventReport model","Galaxy model","MispAttribute model"],"programFiles":["app/Controller/Component/ACLComponent.php","app/Controller/CryptographicKeysController.php","app/Controller/EventsController.php","app/Controller/TagsController.php","app/Model/Event.php","app/Model/EventReport.php","app/Model/Galaxy.php","app/Model/MispAttribute.php"],"repo":"https://github.com/MISP/MISP"}],"references":["https://github.com/MISP/MISP/commit/e4fa73719"],"weaknesses":["CWE-862","CWE-285"],"ingestedAt":"2026-11-19T14:32:06.342Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/133xxx/CVE-2026-133163.json","commit":"14022dca035c4894bf89a896d0435ff9f3d41bea","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-133163","state":"PUBLISHED","datePublished":"2026-11-19T13:55:15.729Z","dateUpdated":"2026-11-19T14:25:18.823Z","assignerShortName":"CIRCL","assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","dateReserved":"2026-11-19T13:55:10.863Z"},"containers":{"cna":{"title":"MISP: External Sync User Can Modify Protected Events Without Signature via Multiple Write Routes","descriptions":[{"lang":"en","value":"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.\n\nAs 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.\n\nThe 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."}],"affected":[{"vendor":"misp","product":"misp","versions":[{"version":"0","status":"affected","lessThanOrEqual":"2.5.51","versionType":"semver"}],"cpes":["cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"],"modules":["ACLComponent","EventsController","TagsController","CryptographicKeysController","Event model","EventReport model","Galaxy model","MispAttribute model"],"programFiles":["app/Controller/Component/ACLComponent.php","app/Controller/CryptographicKeysController.php","app/Controller/EventsController.php","app/Controller/TagsController.php","app/Model/Event.php","app/Model/EventReport.php","app/Model/Galaxy.php","app/Model/MispAttribute.php"],"repo":"https://github.com/MISP/MISP"}],"references":[{"url":"https://github.com/MISP/MISP/commit/e4fa73719","name":"Security patch","tags":["patch"]}],"metrics":[{"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}],"cvssV4_0":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"format":"SSVC","scenarios":[{"lang":"en","value":"GENERAL"}],"other":{"type":"SSVC","content":{"version":"2.0.3","role":"Supplier","timestamp":"2026-11-19T13:50:03Z","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}]}}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-862","lang":"en","description":"CWE-862 Missing Authorization","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-285","lang":"en","description":"CWE-285 Improper Authorization","type":"CWE"}]}],"providerMetadata":{"shortName":"CIRCL","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","dateUpdated":"2026-11-19T13:55:15.729Z"},"x_gcve":[{"recordType":"advisory","extensions":{"bcp-05-x-01":{"ai_annotations":[{"scope":"record","gna_source":1,"tags":["ai-computer-assisted:llm-generated","ai-computer-assisted:classification"],"description":"Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.","ai_level":"generated","review_status":"full","models":[{"name":"qwen3.8:27b","gna_source":1,"source":"ollama","identifier":"qwen3.8:27b"}]}]},"bcp-05-x-02":{"x_patch2vuln":{"generator":"patch2vuln.py","generatedAt":"2026-11-19T13:50:03.083744Z","model":"qwen3.8:27b","source":"https://github.com/MISP/MISP/commit/e4fa73719.patch","patchSha256":"5b0f387b75bb90f531299281ed35699622c3525ee98bdfdad286cbf10af3bdca","patchTruncated":false,"commit":"e4fa7371938d51840ad098e3f727b74f1b5b0831","subject":"fix: [security] Sync users change protected events only","patches":[{"source":"https://github.com/MISP/MISP/commit/e4fa73719.patch","sourceUrl":"https://github.com/MISP/MISP/commit/e4fa73719.patch","patchSha256":"5b0f387b75bb90f531299281ed35699622c3525ee98bdfdad286cbf10af3bdca","commit":"e4fa7371938d51840ad098e3f727b74f1b5b0831","subject":"fix: [security] Sync users change protected events only","date":"Wed, 11 Nov 2026 13:12:32 +0100","retrievedAt":"2026-11-19T13:49:21.953367Z"}],"confidence":"high","assumptions":["Affected version range is unspecified; the patch does not include version tags or release boundaries. All MISP versions prior to this commit are assumed affected.","CVSS SI (subsequent system integrity) is set to N. In practice, a modified protected event could be published to other MISP instances, potentially affecting them, but the patch does not explicitly address or evidence this cross-instance impact.","CAPEC-66 is the closest available mapping; no CAPEC specifically covers 'inconsistent authorization enforcement across multiple endpoints of the same application'.","The assumption that the attacker must belong to the same organization as the event creator (orgc_id match) is based on the existing perm_modify_org and perm_publish checks that were already present; the new check is an additional gate on top of those.","The Co-Authored-By line references an AI assistant (Claude Opus 5.5); it is listed as a tool credit rather than a human remediation developer.","The commit date (2026-11-11) is taken at face value from the patch metadata."],"fixSummary":"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.","patchSummary":"Added Event::isProtectedFromSyncUser() and Event::assertNotProtectedFromSyncUser() methods that return true / throw ForbiddenException when the user has perm_sync but lacks perm_site_admin and perm_sync_internal, and the target event has protected=1. Inserted calls to these methods in: ACLComponent::canModifyEvent(), canPublishEvent(), canModifyTag(); CryptographicKeysController::add() and delete(); EventsController::populate(), upload_sample(), upload_analysis_file(); TagsController::__findObjectByUuid(); Event::userCanModifyEvent() and upload_stix(); EventReport::fetchIfAuthorized(); Galaxy::detachCluster() and detachClusterByTagId(); MispAttribute::deleteAttribute(). Also added the 'protected' field to the event query in upload_sample. Added a comprehensive regression test class (ProtectedEventSyncWrites) covering all affected routes plus control tests for internal sync users, org admins, and post-unprotect behavior.","credits":[{"lang":"en","value":"CERT.pl","type":"reporter"},{"lang":"en","value":"iglocska","type":"remediation developer"},{"lang":"en","value":"Claude Opus 5.5","type":"remediation developer"},{"lang":"en","value":"Claude Opus 5.5","type":"tool"}],"cvssRationale":"AV:N: MISP is a network-accessible web application. AC:L: Exploitation requires only standard API calls with a valid sync user token; no race conditions, timing, or special configuration needed. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with the sync permission (not site admin, not internal sync) in the event's creator organization is required. UI:N: No victim interaction is needed. VC:N: The sync user already has read access to the event; no additional confidentiality exposure. VI:H: The attacker can fully modify, delete, add, and unprotect event data, completely defeating the integrity guarantee of the protection mechanism. VA:N: No denial-of-service impact is evident. SC/SI/SA:N: No evidence in the patch of direct impact on subsequent systems; cross-instance impact via publish is possible but not explicitly addressed in the patch evidence.","ssvc":{"version":"2.0.3","role":"Supplier","timestamp":"2026-11-19T13:50:03Z","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}]},"weaknessRationale":[{"cweId":"CWE-862","rationale":"The event protection authorization check was present only on the events/edit route. All other write endpoints (attributes, objects, populate, publish, unprotect, tags, reports, galaxy clusters, cryptographic keys) lacked the equivalent check, allowing a sync user to bypass the protection mechanism entirely."},{"cweId":"CWE-285","rationale":"The authorization logic did not correctly account for the combination of sync-user role and event protection state across all code paths, resulting in an inconsistent enforcement of the protection policy."}],"capecRationale":[{"capecId":"CAPEC-66","rationale":"The access control policy for protected events was incorrectly configured: the protection check was applied to only one of many write endpoints. An attacker with a valid sync user account exploited the missing checks on the remaining endpoints to modify protected events. This is the closest CAPEC to the observed pattern of a partially enforced access control rule. Uncertainty: CAPEC-66 is a broad category; a more specific sub-pattern for 'inconsistent authorization enforcement across endpoints' does not exist in the CAPEC taxonomy, so this is the best available match."}],"draft":false,"modelComparison":{"selectedModel":"qwen3.8:27b","selectionMethod":"deterministic-consensus-v1","selectionNotice":"The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.","rankings":[{"model":"qwen3.8:27b","score":7,"agreementScore":11,"confidence":"high","assumptionCount":6}],"potentialErrors":[]}}},"bcp-05-x-03":{"x_timeline":{"events":[{"type":"fix-developed","timestamp":"2026-11-11T12:12:32Z","description":"Corrective change authored (e4fa7371938d51840ad098e3f727b74f1b5b0831): fix: [security] Sync users change protected events only","references":["https://github.com/MISP/MISP/commit/e4fa73719.patch"],"id":"evt-fix-developed-1"},{"id":"evt-fix-available-1","type":"fix-available","timestamp":"2026-11-19T13:49:21.953367Z","description":"Patch retrieved from the supplied URL; retrieval time is used as the default availability time.","references":["https://github.com/MISP/MISP/commit/e4fa73719.patch"]}]}}},"vulnId":"gcve-1-2026-20180"}],"solutions":[{"lang":"en","value":"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."}],"impacts":[{"capecId":"CAPEC-66","descriptions":[{"lang":"en","value":"CAPEC-66 Exploiting Incorrectly Configured Access Control"}]}],"credits":[{"lang":"en","value":"CERT.pl","type":"reporter"},{"lang":"en","value":"iglocska","type":"remediation developer"},{"lang":"en","value":"Claude Opus 5.5","type":"remediation developer"},{"lang":"en","value":"Claude Opus 5.5","type":"tool"}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*","versionStartIncluding":"0","versionEndIncluding":"2.5.51"}]}]}]},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-11-19T14:24:34.101519Z","id":"CVE-2026-133163","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-11-19T14:25:18.823Z"}}]}}}