# CVE-2026-104910: MISP Information Disclosure via Related Events Listing Bypassing Per-Event Authorization

> Authenticated users can view metadata of unauthorized threat intelligence events due to missing access checks in related event listings.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-qxmx-5j2w-4wjc

## What is CVE-2026-104910?

CVE-2026-104910 is a medium-severity missing authorization vulnerability in MISP, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MISP contains an authorization bypass in the related events listing functionality. When a user requests the list of events correlated to a given event, the system retrieved related event metadata directly from the correlation table without re-validating the caller's access rights against each related event.

The correlation table stores a snapshot of the event's distribution level and sharing group at the time the correlation was created, and does not carry the published flag. As a result, events that the caller is not permitted to open—because they are unpublished, or because their distribution or sharing group has changed since the correlation was recorded—were still returned with their metadata (title, date, correlating value counts).

Preconditions:

- An authenticated user with access to at least one event in MISP.

- The existence of correlation entries linking that event to other events the user should not be able to view.

Impact:

- Unauthorized disclosure of event metadata (titles, dates, correlation counts) for events the user has no right to access.

- Potential reconnaissance of threat-intelligence event names and timelines across sharing groups.

Affected: MISP versions prior to the fix commit (2ffa97f05).

Weakness: CWE-862 (Missing Authorization), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-104910?


## How do I fix CVE-2026-104910?

No fix has been published for CVE-2026-104910 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104910 being exploited?

There is no known exploitation of CVE-2026-104910 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104910 and fix it if it is affected.

What it is: CVE-2026-104910 is a medium-severity missing authorization vulnerability in MISP, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104910 in the wild and no public exploit code.

Affected product: MISP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104910/ (Markdown: https://insights.sbomify.com/CVE-2026-104910/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104910
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104910
- OSV: https://osv.dev/vulnerability/CVE-2026-104910

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104910/
Summaries are generated and may contain mistakes; the official description above is the record.