# CVE-2026-86441: MISP Dashboard Organisation Widgets Bypass Organisation-Index Restrictions and Expose Hidden Organisation Data

> Authenticated users can bypass organisation visibility restrictions to enumerate hidden organisations and access sensitive data via dashboard widgets.

- **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:** 8 Sep 2026
- **Also known as:** GHSA-6x2c-442p-85rw

## What is CVE-2026-86441?

CVE-2026-86441 is a low-severity missing authorization 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 contain inconsistent authorization checks across dashboard widgets that display organisation information.

Several organisation-related widgets did not honor Security.hide_organisation_index_from_users. As a result, authenticated users without the perm_sharing_group permission could enumerate organisations even though the normal organisation index was intentionally hidden from them.

The affected widgets included paths that:

  *  
returned organisation names and identifiers;

  *  
could expose additional organisation database fields through JSON export because unrestricted find('all') queries fetched full rows;

  *  
accepted limit=0 or negative values in a way that could effectively remove the result limit and return the entire organisation table.

A related organisation-contributor leaderboard also ignored the same visibility setting. Its handler counted Event.orgc_id across the entire event table and mapped those IDs to organisation names, revealing every organisation with events regardless of whether the caller could see any of those events. The fix withdraws this widget entirely for users who lack organisation-index 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-86441?

It affects 1 product.


Products: Misp-Project Misp.

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

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

## Is CVE-2026-86441 being exploited?

There is no known exploitation of CVE-2026-86441 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-86441 and fix it if it is affected.

What it is: CVE-2026-86441 is a low-severity missing authorization 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-86441 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-86441/ (Markdown: https://insights.sbomify.com/CVE-2026-86441/index.md)
```

## Sources

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

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