No advisories yet.
Solution
The tag endpoints now load their target event or attribute using ACL-aware fetch methods (fetchSimpleEvent, fetchAttributeSimple) that apply the calling user's visibility rules before returning the object. A hidden event or attribute now produces the same response as a non-existent one, eliminating both the tag-enumeration information leak and the ability of host-organisation users to modify tags on records they cannot see. A clarifying comment was added to ACLComponent::canModifyTag to document that the caller must load the object with visibility applied first.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://github.com/MISP/MISP/commit/de1a25aa0 |
|
Wed, 18 Nov 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MISP contains an access control flaw in its tag management endpoints: events/addTag (single and bulk), events/removeTag, and attributes/removeTag. These endpoints loaded their target event or attribute using an unscoped database query (recursive = -1) that did not apply the calling user's ACL visibility rules. As a result, two distinct security issues existed: (1) Information disclosure: the removeTag endpoint returned different responses depending on whether a given tag was present on a hidden event, allowing an authenticated user to enumerate which tags were applied to events they had no visibility into. (2) Unauthorized modification: users belonging to the host organisation, who are permitted to set local tags on records they can see, could add or remove local tags on events and attributes they could not see, because the canModifyTag ACL check operated on the unscoped object without first verifying the caller's visibility. The fix replaces the unscoped find() calls with ACL-aware fetch methods (fetchSimpleEvent and fetchAttributeSimple) that apply the user's visibility before the object is returned, and adds an explicit empty-object check in removeTag so that a hidden event responds identically to a non-existent one. Affected components include the EventsController (addTag, removeTag), the AttributesController (removeTag), and the ACLComponent (canModifyTag). The vulnerability requires an authenticated user with at least the tagger role (perm_tagger) or host-organisation membership. | |
| Title | MISP Tag Endpoints Bypass ACL Visibility, Allowing Unauthorized Tag Modification and Enumeration on Hidden Events | |
| First Time appeared |
Misp
Misp misp |
|
| Weaknesses | CWE-200 CWE-862 |
|
| CPEs | cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Misp
Misp misp |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-18T21:25:48.929Z
Reserved: 2026-11-18T21:04:45.661Z
Link: CVE-2026-132642
No data.
Status : Deferred
Published: 2026-11-18T21:17:58.313
Modified: 2026-11-18T21:17:58.427
Link: CVE-2026-132642
No data.
OpenCVE Enrichment
No data.