CVE-2026-78583: Elastic Kibana privilege escalation via Fleet integration validation bypass

CVE-2026-78583 · Severity: high · CVSS 8.1 · Published 2026-09-03

Kibana's Fleet feature, which manages and deploys monitoring agents across infrastructure, fails to validate privilege declarations from integration packages. An attacker with Fleet management privileges can craft malicious integration configurations to grant enrolled Elastic Agents arbitrarily high privileges, including full cluster administration, affecting all agents controlled by a targeted policy.

Technologies: Elastic Kibana. Vendors: Elastic.

Quick answers

Is CVE-2026-78583 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-78583 being exploited in the wild.
How severe is CVE-2026-78583?
High severity, with a CVSS score of 8.1, published 3 September 2026.
Which products and versions are affected?
Elastic Kibana 8.0.0 to 8.19.20, 9.0.0 to 9.4.5, 9.5.0 to 9.5.2.
Is there a fix for CVE-2026-78583?
A patch was published on 2026-09-03: Fixed in Kibana 8.19.21, 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-78583 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-78583?
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

This is an authorization bypass vulnerability (CWE-863) in Kibana's Fleet agent management system. The root cause is insufficient validation of Elasticsearch cluster privilege declarations originating from integration packages before these privileges are used to mint credentials for enrolled Elastic Agents. An authenticated attacker with Fleet management privileges can manipulate integration package data to inject elevated privilege claims that are trusted without validation. The attack requires both Fleet integration management and agent policy management privileges held simultaneously. Successful exploitation results in arbitrary privilege escalation up to and including full Elasticsearch cluster administration on all agents in the targeted policy. The vulnerability is patched in Kibana 8.19.21, 9.4.6, and 9.5.3.

Affected products

  • Elastic Kibana 8.0.0 to 8.19.20, 9.0.0 to 9.4.5, 9.5.0 to 9.5.2

Timeline

  • 2026-09-03: disclosed
  • 2026-09-03: patched: Fixed in Kibana 8.19.21, 9.4.6, and 9.5.3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.