CVE 8.8 HIGH

MISP mass assignment vulnerabilities allow unauthorized modification of ownership and delegation records_CVE-2026-54361

8.8 / 10
HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N

Description

MISP contained multiple mass assignment vulnerabilities in the handling of collections, tag collections, event delegations, and shadow attributes. Several controller actions accepted user-supplied fields that should have remained server-controlled, including record identifiers and ownership-related fields such as id, org_id, orgc_id, and user_id.

An authenticated attacker with access to the affected endpoints could craft requests containing protected fields in order to alter object ownership, redirect an update to another record, overwrite existing event delegation requests, or modify shadow attribute proposals belonging to another organization. This could result in unauthorized modification of MISP objects and, depending on object visibility and sharing configuration, unauthorized access to or transfer of sensitive threat intelligence data.

The issue was fixed by explicitly pinning ownership and identity fields to their stored values during edit operations and by removing user-supplied primary keys from create-only save paths.

Affected components:

* CollectionsController::edit()
* EventDelegationsController::delegateEvent()
* ShadowAttributesController::edit()
* TagCollectionsController::edit()915
* TagCollectionsController::editWithTags()


Attack requirements:
The attacker must be authenticated and able to reach the affected MISP endpoints. No user interaction is required.

AI Analysis

MISP mass assignment vulnerability allowing unauthorized modification of ownership and delegation records

Basic Information

ID CVE-2026-54361
Source CIRCL
Published Jun 12, 2026 at 19:59

Affected Product

Vendor misp
Product misp
Affected Versions misp misp 0

CWE Classification

AI Assessment

AI Score 8.8 / 10
AI Severity High
Vendor MISP
Product MISP

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.