CVE-2026-72630: Incorrect Authorization in Kibana Fleet Leading to Privilege Escalation
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72630?
The severity of CVE-2026-72630 is rated high with a score of 7.1.
What are the potential impacts of CVE-2026-72630?
CVE-2026-72630 can lead to privilege escalation through Incorrect Authorization in Kibana Fleet.
How can I fix CVE-2026-72630?
Fixing CVE-2026-72630 involves updating to the latest version of Elastic Kibana Fleet where the vulnerability is addressed.
Who is affected by CVE-2026-72630?
Users of Elastic Kibana Fleet may be affected by CVE-2026-72630 due to the privilege escalation risk.
What type of vulnerability is CVE-2026-72630 categorized as?
CVE-2026-72630 is categorized as Incorrect Authorization, which falls under CWE-863.