CVE-2026-54361: MISP mass assignment vulnerabilities allow unauthorized modification of ownership and delegation records

Published Jun 12, 2026
·
Updated

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, orgid, orgcid, and userid.

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.

Affected Software

1 affected component
Misp Project Misp

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    During edit operations, explicitly assign the stored values for id, org_id, orgc_id, and user_id instead of accepting these fields from user-supplied parameters so ownership and identifiers cannot be modified by clients.

    CollectionsController::edit pinned_fields = id, org_id, orgc_id, user_id pinned to stored values
  2. Configuration

    During delegation/edit operations, explicitly assign the stored values for id, org_id, orgc_id, and user_id instead of accepting these fields from user-supplied parameters to prevent overwriting or redirecting delegations.

    EventDelegationsController::delegateEvent pinned_fields = id, org_id, orgc_id, user_id pinned to stored values
  3. Configuration

    During edit operations, explicitly assign the stored values for id, org_id, orgc_id, and user_id rather than accepting them from clients so shadow attribute proposals cannot be altered to belong to a different organization.

    ShadowAttributesController::edit pinned_fields = id, org_id, orgc_id, user_id pinned to stored values
  4. Configuration

    During tag collection edit operations (including editWithTags), explicitly assign the stored values for id, org_id, orgc_id, and user_id instead of accepting these fields from user input to prevent unauthorized ownership modification.

    TagCollectionsController::edit / TagCollectionsController::editWithTags pinned_fields = id, org_id, orgc_id, user_id pinned to stored values
  5. Configuration

    Remove user-supplied primary keys (for example id and other DB primary key fields) from permitted/accepted parameters on create-only save paths so clients cannot set primary keys when creating new records.

    create-only save paths permit_primary_keys = false
  6. Compensating control

    Restrict network access to the affected MISP endpoints to trusted IP ranges or via VPN/WAF rules and ensure access requires authentication; limit exposure while fixes are being developed and deployed.

  7. Operational

    Audit logs and database records for changes to ownership-related fields (id, org_id, orgc_id, user_id), event delegations, shadow attributes, and tag collections; identify and revert any unauthorized modifications and notify affected stakeholders.

Event History

Jun 12, 2026
CVE Published
via MITRE·07:59 PM
Data Sourced
via MITRE·07:59 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-54361?

CVE-2026-54361 has a high severity rating of 8.8 according to the CVSS scoring system.

2

How do I fix CVE-2026-54361?

To fix CVE-2026-54361, upgrade to the patched version of MISP provided in the project's repository.

3

What kind of vulnerabilities are associated with CVE-2026-54361?

CVE-2026-54361 is associated with mass assignment vulnerabilities that allow unauthorized modification of ownership and delegation records.

4

What impact does CVE-2026-54361 have on MISP?

CVE-2026-54361 allows attackers to modify critical data such as record identifiers and ownership-related fields, leading to potential unauthorized access.

5

When was CVE-2026-54361 published?

CVE-2026-54361 was published on June 12, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203