CVE-2026-72629: CWE-639 Authorization Bypass Through User-Controlled Key in Elastic Kibana
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized cross-space access via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). The result is disclosure of inference output from a trained model in a different space that the user is not authorized to list, read, or use, which exposes the behavior of a model. The same pattern also reached the deployment stop and deployment update operations, allowing an active trained model deployment in another space to be stopped or to have its allocated resources altered.
AI Analysis
Technical Summary
This vulnerability (CWE-639) in Kibana permits an attacker with some privileges to bypass authorization controls by exploiting user-controlled keys. It enables unauthorized access to inference outputs of trained models in different spaces, which the attacker is not authorized to list, read, or use. Additionally, it allows stopping or updating active trained model deployments in other spaces, potentially altering allocated resources. The vulnerability is identified in Kibana versions 8.19.0, 9.0.0, and 9.5.0. The CVSS 3.1 score is 7.1 (high severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity impact, and low availability impact.
Potential Impact
Successful exploitation leads to unauthorized disclosure of trained model inference outputs from other spaces, exposing sensitive model behavior. It also permits unauthorized stopping or updating of active model deployments in other spaces, which could disrupt model availability or alter resource allocation. There is no reported impact on integrity, but confidentiality is highly affected and availability impact is low.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is indicated in the provided data. Users should monitor Elastic's advisories for updates and apply patches once available. Until then, restrict user privileges and monitor access to trained model functionalities to minimize risk.
CVE-2026-72629: CWE-639 Authorization Bypass Through User-Controlled Key in Elastic Kibana
Description
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized cross-space access via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). The result is disclosure of inference output from a trained model in a different space that the user is not authorized to list, read, or use, which exposes the behavior of a model. The same pattern also reached the deployment stop and deployment update operations, allowing an active trained model deployment in another space to be stopped or to have its allocated resources altered.
CVSS v3.1
Score 7.1high
Affected software
pkg:github/elastic/kibanaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CWE-639) in Kibana permits an attacker with some privileges to bypass authorization controls by exploiting user-controlled keys. It enables unauthorized access to inference outputs of trained models in different spaces, which the attacker is not authorized to list, read, or use. Additionally, it allows stopping or updating active trained model deployments in other spaces, potentially altering allocated resources. The vulnerability is identified in Kibana versions 8.19.0, 9.0.0, and 9.5.0. The CVSS 3.1 score is 7.1 (high severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity impact, and low availability impact.
Potential Impact
Successful exploitation leads to unauthorized disclosure of trained model inference outputs from other spaces, exposing sensitive model behavior. It also permits unauthorized stopping or updating of active model deployments in other spaces, which could disrupt model availability or alter resource allocation. There is no reported impact on integrity, but confidentiality is highly affected and availability impact is low.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is indicated in the provided data. Users should monitor Elastic's advisories for updates and apply patches once available. Until then, restrict user privileges and monitor access to trained model functionalities to minimize risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- elastic
- Date Reserved
- 2026-08-10T11:17:29.887Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e1a7fbf8831d539b180e0
Added to database: 08/13/2026, 19:26:55 UTC
Last enriched: 08/13/2026, 19:56:28 UTC
Last updated: 08/13/2026, 23:01:03 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.
External Links
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.