Quick answers
- Is CVE-2026-78595 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78595 being exploited in the wild.
- How severe is CVE-2026-78595?
- Medium severity, with a CVSS score of 4.3, published 3 September 2026.
- Which products and versions are affected?
- Elastic Kibana 9.1.0 to 9.4.5, 9.5.0 to 9.5.2.
- Is there a fix for CVE-2026-78595?
- A patch was published on 2026-09-03: Fixed in Kibana 9.4.6 and 9.5.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78595 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-78595?
- Check whether you run Elastic Kibana at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a missing authorization check (CWE-862) in Kibana's Fleet plugin that fails to properly enforce space-level access controls. An authenticated user holding read-level Fleet agent privileges in one Kibana space can enumerate and access agent metadata and diagnostic content from agents in other spaces, bypassing intended isolation. The attack requires network access and prior authentication, with no user interaction needed. The flaw affects Kibana 9.x versions 9.1.0–9.4.5 and 9.5.0–9.5.2 when Fleet space awareness is enabled (default in new 9.x installations); it is resolved in versions 9.4.6 and 9.5.3.
Affected products
- Elastic Kibana 9.1.0 to 9.4.5, 9.5.0 to 9.5.2
Timeline
- 2026-09-03: disclosed
- 2026-09-03: patched: Fixed in Kibana 9.4.6 and 9.5.3