CVE-2026-72630: Kibana Fleet Leading to Privilege Escalation · Incorrect Authorization
Affects kibanaSource GCVE Database
Not known to be exploited · CVSS 7.1 High · fixed in 9.5.1 : patch kibana soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.5.1, 9.4.5, 8.19.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade kibana to 9.5.1, 9.4.5 or 8.19.20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikibanapkg:bitnami/kibanaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should upgrade Kibana Fleet to a fixed version beyond the affected ranges. Specifically, versions >=8.19.0 and <8.19.20, >=9.0.0 and <9.4.5, and >=9.5.0 and <9.5.1 are vulnerable. Upgrading to versions 8.19.20 or later, 9.4.5 or later, and 9.5.1 or later respectively will remediate the issue. No additional mitigation steps are indicated.
Description
CVE-2026-72630 is a high-severity vulnerability in Kibana Fleet involving incorrect authorization that allows privilege escalation. The flaw occurs because Fleet restricts management of integration policies to specific integrations, but when updating an existing policy, the authorization check is performed against the stored integration rather than the new integration supplied. This enables an authenticated user with Elastic Defend endpoint policy management privileges to convert an endpoint policy they control into a policy for a different integration and supply that integration's configuration.