Quick answers
- Is CVE-2026-104910 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104910 being exploited in the wild.
- How severe is CVE-2026-104910?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- MISP Project MISP prior to commit 2ffa97f05.
- Is there a fix for CVE-2026-104910?
- Yes: fixed in commit 2ffa97f05 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104910 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104910?
- Check whether you run MISP Project MISP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: commit 2ffa97f05 and later
Technical details
The related events listing functionality fails to re-validate the caller's access rights when retrieving correlated events from the correlation table. The system uses stale distribution and sharing group snapshots stored at correlation time, which do not reflect unpublished flag changes or updates to sharing permissions after the correlation was created. An authenticated attacker with access to at least one event can enumerate metadata of inaccessible related events.
Affected products
- MISP Project MISP prior to commit 2ffa97f05
Timeline
- 2026-10-02: disclosed