CVE-2026-132643: MISP Anonymised Sightings Reporter Identity Disclosure via Organisation Filter

Published Nov 18, 2026
·
Updated

MISP contains an information disclosure vulnerability in the Sighting model when the Sightingsanonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied orgid filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter's organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation's ID in the filter. The query would then return only that organisation's sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (permsighting) who is not a site administrator, and the Sightingsanonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.

Affected Software

1 affected component
Misp Project Misp

Event History

Nov 18, 2026
CVE Published
via MITRE·09:08 PM
Data Sourced
via MITRE·09:08 PM
RemedyDescriptionWeakness
Data Sourced
via OSV·09:08 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

The issue applies only when the Sightings_anonymise plugin setting is enabled. Deployments that do not enable this anonymization setting are not affected by this specific bypass.

2

What access does an attacker need?

An attacker must be authenticated as a non-site-admin user with sighting read permission (perm_sighting). No user interaction is required.

3

How can the anonymization be bypassed?

A permitted user can supply another organisation's ID through the org_id filter accepted by listSightings or sightings/restSearch. A negated NOT IN filter can also reveal the target organisation's sightings by showing which records are excluded.

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