CVE-2026-95671: MISP Collections: Missing Authorization Check for Sharing Group on PUT Request in collections/add

Published Sep 22, 2026
·
Updated

In MISP, the CollectionsController add() method enforced the sharing-group usability authorization check and element capture only when the HTTP request method was POST. However, the underlying CRUDComponent::add() method persists data on both POST and PUT requests. As a result, an authenticated user could issue a PUT request to the collections/add endpoint, bypassing the sharing-group authorization check entirely. This allowed the creation of a collection with distribution=4 (shared with a specific sharing group) targeting a sharing group that the user was not authorized to use. The bypassed check would normally verify that the current user has access to the specified sharing group before allowing the collection to be associated with it.

The security impact is that an authenticated user can place collection data into a sharing group context they do not have legitimate access to, potentially exposing that data to all members of the unauthorized sharing group and violating the intended access-control boundaries of the MISP instance.

The vulnerability requires an authenticated session and knowledge of a valid sharing group identifier; no user interaction or special tooling is needed beyond sending a PUT request instead of a POST request to the same endpoint.

Affected Software

1 affected component
Misp Misp

Event History

Sep 22, 2026
CVE Published
via MITRE·01:20 PM
Data Sourced
via MITRE·01:20 PM
RemedyDescriptionWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs an authenticated MISP session and knowledge of a valid sharing group identifier. No user interaction or special tooling is required.

2

What data exposure can result from exploitation?

An authenticated user can create a collection associated with a sharing group they are not authorized to use. Collection data may then be exposed to all members of that sharing group, crossing intended access-control boundaries.

3

What request pattern is affected?

The authorization check is enforced for POST requests to collections/add but can be bypassed with a PUT request. The underlying add operation persists data for both request methods.

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