CVE-2026-94393: MISP Event Report Cross-Event Reparenting via Unscoped UUID Resolution in editReport

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 29 Oct 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.4%

EPSS score, percentile 31.1 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

6.4 Medium

CVSS v4.0 base score, given by the CNA

What should I do?

The fix adds an ownership check in editReport: before adopting an existing report found by UUID … Full textSolution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (1)

Which versions are affected?

Affected

• before 2.5.47

Versions by product

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026; CVE List, as of 29 Oct 2026. About the data.

What to do

Solution (from the CVE record)

The fix adds an ownership check in editReport: before adopting an existing report found by UUID, the code now verifies that the report's event_id matches the event being edited. If the UUID resolves to a report belonging to a different event, the operation is rejected with an error message, preventing cross-event reparenting, unauthorized read, and unauthorized overwrite of reports.

Advisories and patches

• Security patch (Patch)

This summary is based on the CVE record as of 29 Oct 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

Source: CVE List, as of 29 Oct 2026. About the data.

About this vulnerability

When a user creates or edits a report inside an event, MISP can identify an existing report using its UUID without properly checking whether that report actually belongs to the same event. As a result, a user who has editing rights on one event could potentially move a report from another event into their own event, as long as they know or can guess the report’s UUID. Once moved, they could view…

Summary: CVE record, as of 29 Oct 2026.

• CISA has not added CVE-2026-94393 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
• The CVE record was published on 21 Sep 2026.
• The CVE record carries a CVSS v4.0 base score of 6.4 (Medium), given by its CNA.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.4% (percentile 31.1), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
• CISA's SSVC assessment in the CVE record: exploitation none, automatable no, technical impact partial.
• The credits in the CVE record name Anthropic (Claude) as finder.

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; CVE List, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026. About the data.

Description

MISP Event Report Cross-Event Reparenting via Unscoped UUID Resolution in editReport

When a user creates or edits a report inside an event, MISP can identify an existing report using its UUID without properly checking whether that report actually belongs to the same event. As a result, a user who has editing rights on one event could potentially move a report from another event into their own event, as long as they know or can guess the report’s UUID. Once moved, they could view and change information that they were not originally allowed to access. The vulnerability requires the attacker to have editor access to at least one event and to know or discover a valid report UUID. The main impact is that private event reports could be exposed or modified across event boundaries, bypassing MISP’s normal access restrictions. Version affected: <2.5.47

Source: CVE List, as of 29 Oct 2026. About the data.

Timeline