# CVE-2026-86283: MISP UiBeta Collection View Bypasses Event ACL, Exposing Unauthorized Event Data

> Authenticated users can bypass event access controls in MISP's UiBeta theme to view unauthorized event details, leading to horizontal privilege escalation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/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:** 6 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-p286-r3vc-q86q

## What is CVE-2026-86283?

CVE-2026-86283 is a high-severity missing authorization vulnerability in MISP, published on 6 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MISP's UiBeta theme collection view (app/View/Themed/UiBeta/Collections/view.ctp) performed a secondary query of member events by UUID without applying the caller's access control list (ACL). The CollectionsController::view() action correctly resolved collection element UUIDs through Event::fetchSimpleEvents($user, ...), which enforces per-user event ACL. However, the view template independently re-queried the same UUIDs using only an Event.uuid IN (...) condition, omitting the createEventConditions() authorization filter. Because collection element UUIDs are stored without server-side authorization against the referenced event (CollectionElementsController::add() accepts whatever UUID the collection owner posts), an authenticated user with view access to a collection could retrieve full details of events they are not permitted to read. The exposed data included event identifiers, info, dates, timestamps, creator organization, all event tags, and galaxy clusters (the latter attached via a cluster-scoped rather than event-scoped ACL check). This constitutes an authorization bypass at the presentation layer, allowing horizontal privilege escalation across event boundaries within the MISP instance.

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

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


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

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

## Is CVE-2026-86283 being exploited?

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

Public exploit code:

- Autonomous AI agent with its own crypto identity — hunts CVEs, builds exploit labs, validates vulnerabilities (first public PoC of CVE-2026-86283), trades crypto 24/7 to fund itself. Sentric Research. (github_poc): https://github.com/Freire007-byte/sentric-core

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86283 is a high-severity missing authorization vulnerability in MISP, published on 6 Sep 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-86283 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-86283/ (Markdown: https://insights.sbomify.com/CVE-2026-86283/index.md)
```

## Sources

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

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