In this article
MISP sightings flaw defeats the anonymisation setting
MISP leaks which organisation reported a sighting when the Sightings_anonymise setting is enabled, which undermines the feature meant to hide that. NVD scores CVE-2026-132643 at 5.3 under CVSS 4.0, rated medium. The issue was reported by ENISA, according to the NVD record.
An org_id filter exposes who reported a sighting
The listSightings and sightings/restSearch endpoints accept an org_id filter and pass it to the SQL query without an authorisation check. A user who is not a site admin can supply another organisation's ID, get back that organisation's sightings and so identify the reporter. A negated filter (NOT IN) also reveals the targeted organisation's sightings, by exclusion. Anonymisation normally masks the reporter's organisation in the records these endpoints return.
Who can trigger it on a MISP instance
The attacker must be an authenticated user with sighting read permission (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be on. The CVSS vector shows network access, low attack complexity and low privileges required. If your instance does not use Sightings_anonymise, the conditions in the record are not met.
The NVD record gives no affected version range. It does not say whether the flaw has been exploited in the wild or added to CISA's KEV catalog.
No fixed MISP version is listed yet
NVD lists the CVE as Deferred and names no fixed version. It does reference MISP GitHub commit 415f07967 for this CVE. The record gives no workaround and no patch release date.
Review who holds sighting access in MISP
With no fixed release named, check whether Sightings_anonymise is enabled on your instance and which non-admin users have perm_sighting. Those two conditions decide whether the flaw can be reached.
Sources
Image: Photo by Shahadat Rahman on Unsplash
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].



Discussion