Skip to content
Fencer Intel
high 7.1

CVE-2026-72630 json

Incorrect Authorization in Kibana Fleet Leading to Privilege Escalation

published 2mo ago modified 2mo ago also BIT-elk-2026-72630 , BIT-kibana-2026-72630 , EUVD-2026-58290

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

Incorrect Authorization (CWE-863) in Kibana Fleet can lead to privilege escalation via Privilege Abuse (CAPEC-122). Fleet restricts some callers to managing integration policies for one specific integration. When an existing integration policy was updated, that restriction was evaluated against the integration recorded on the stored policy rather than against the replacement integration supplied with the update. An authenticated user holding only the Elastic Defend endpoint policy management privilege was therefore able to convert an endpoint policy they administer into a policy for a different integration, and to supply that integration's configuration at the same time.

Patch / fix

  • bitnami elk 8.19.20, 9.4.5, 9.5.1
  • bitnami kibana 8.19.20, 9.4.5, 9.5.1
  • elastic kibana 8.19.20, 9.4.5, 9.5.1
  • elasticsearch kibana 8.19.20, 9.4.5, 9.5.1

Is CVE-2026-72630 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
OSV 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami elk
>=8.19.0, <8.19.20
>=9.0.0, <9.4.5
>=9.5.0, <9.5.1
8.19.20
9.4.5
9.5.1
bitnami kibana
>=8.19.0, <8.19.20
>=9.0.0, <9.4.5
>=9.5.0, <9.5.1
8.19.20
9.4.5
9.5.1

Affected products

  • Elastic Kibana

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.