# CVE-2026-86418: MISP Dashboard Organisation Picker Exposes Hidden Organisation Metadata to Unauthorized Users

> Authenticated users can view hidden organisation metadata via the dashboard picker when specific security settings are enabled, bypassing intended visibility restrictions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** 7 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-jmv6-hcw6-r4f7

## What is CVE-2026-86418?

CVE-2026-86418 is a low-severity vulnerability in Misp-Project Misp, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected versions of MISP expose organisation metadata through the dashboard organisation picker without applying the same visibility restrictions enforced by the normal organisation index and per-organisation view.

The affected endpoint returned fields including:

 - organisation ID;

 - UUID;

 - name.

When Security.hide_organisation_index_from_users was enabled, normal organisation enumeration was restricted, but the dashboard picker still queried all organisations. This allowed authenticated users to discover organisations that should have remained hidden from them.

The fix calls Organisation::createConditions($this->Auth->user()) and appends the resulting ACL conditions to the picker query. Ordinary users are thereby limited to organisations associated with events or proposals they can already see, plus their own organisation, while users with the appropriate sharing-group privilege retain broader visibility.

Version affected: ≤2.5.45

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Misp-Project Misp.

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

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

## Is CVE-2026-86418 being exploited?

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

## Other vulnerabilities in Misp-Project Misp

- [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8)
- [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8)
- [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86418 is a low-severity vulnerability in Misp-Project Misp, published on 7 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-86418 in the wild and no public exploit code.

Affected product: Misp-Project 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-86418/ (Markdown: https://insights.sbomify.com/CVE-2026-86418/index.md)
```

## Sources

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

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