# CVE-2026-78595: Missing Authorization in Kibana Fleet Plugin Leading to Cross-Space Agent Data Disclosure

> An authenticated user with read-level Fleet privileges can access agent metadata and diagnostics from other Kibana spaces due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** BIT-elk-2026-78595, BIT-kibana-2026-78595, GHSA-xvx8-crx2-xjwv, MINI-5mwg-vhgg-j3mp, MINI-829q-vphj-whg2, MINI-jq4g-p4v3-v5vq, MINI-vc6p-chv5-4gc2, MINI-w85w-q7gx-gj85

## What is CVE-2026-78595?

CVE-2026-78595 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization in Kibana Leading to Information Disclosure / Missing Authorization (CWE-862) in the Kibana Fleet feature can lead to information disclosure via Privilege Abuse (CAPEC-122). An authenticated user holding read-level Fleet agent privileges in one Kibana space could enumerate agent metadata and access diagnostic content belonging to agents enrolled in other Kibana spaces.

Weakness: CWE-862 (Missing Authorization)

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

2 open source packages ship an affected version, including kibana and elk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kibana` | Bitnami | From 9.1.0 | 9.4.6, 9.5.3 |
| `elk` | Bitnami | From 9.1.0 | 9.4.6, 9.5.3 |

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

Upgrade kibana to a fixed version for your release line: 9.4.6 or 9.5.3.

## Is CVE-2026-78595 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78595 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 3 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-78595 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 9.1.0; fixed in 9.4.6, 9.5.3
- elk (Bitnami): affected from 9.1.0; fixed in 9.4.6, 9.5.3

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-78595/ (Markdown: https://insights.sbomify.com/CVE-2026-78595/index.md)
```

## Sources

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

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