Elk: Incorrect Authorization in Kibana Fleet Leading to Privilege Escalation (CVE-2026-72630)
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.
AI Analysis
Technical Summary
The vulnerability in Kibana Fleet (CVE-2026-72630) arises from incorrect authorization logic (CWE-863) during updates to integration policies. Fleet enforces restrictions so that callers can manage policies only for a specific integration. However, when an existing integration policy is updated, the authorization check is incorrectly applied against the integration recorded on the stored policy instead of the replacement integration provided in the update request. This flaw allows an authenticated user with limited privileges (Elastic Defend endpoint policy management) to escalate privileges by converting an endpoint policy they administer into a policy for a different integration and supplying that integration's configuration simultaneously.
Potential Impact
An authenticated user with Elastic Defend endpoint policy management privileges can escalate their privileges by modifying integration policies beyond their intended scope. This could lead to unauthorized configuration changes in integrations other than those they are permitted to manage, potentially compromising system integrity or security posture.
Mitigation Recommendations
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.
Elk: Incorrect Authorization in Kibana Fleet Leading to Privilege Escalation (CVE-2026-72630)
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.
Affected software
pkg:bitnami/kibanaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Kibana Fleet (CVE-2026-72630) arises from incorrect authorization logic (CWE-863) during updates to integration policies. Fleet enforces restrictions so that callers can manage policies only for a specific integration. However, when an existing integration policy is updated, the authorization check is incorrectly applied against the integration recorded on the stored policy instead of the replacement integration provided in the update request. This flaw allows an authenticated user with limited privileges (Elastic Defend endpoint policy management) to escalate privileges by converting an endpoint policy they administer into a policy for a different integration and supplying that integration's configuration simultaneously.
Potential Impact
An authenticated user with Elastic Defend endpoint policy management privileges can escalate their privileges by modifying integration policies beyond their intended scope. This could lead to unauthorized configuration changes in integrations other than those they are permitted to manage, potentially compromising system integrity or security posture.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-kibana-2026-72630
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2026-72630"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- High
- Cvss Version
- null
Threat ID: 6a85b4aaacd9273b49250f30
Added to database: 08/19/2026, 13:50:34 UTC
Last enriched: 08/19/2026, 14:06:52 UTC
Last updated: 08/19/2026, 15:52:01 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.