Elastic Kibana up to 8.19.18/9.3.7/9.4.3 Machine Learning resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 3.35 |
Summary
A vulnerability was found in Elastic Kibana up to 8.19.18/9.3.7/9.4.3. It has been rated as problematic. This impacts an unknown function of the component Machine Learning. This manipulation causes resource consumption. The identification of this vulnerability is CVE-2026-63261. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Elastic Kibana up to 8.19.18/9.3.7/9.4.3. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Machine Learning. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can send a specially crafted request to a Kibana machine learning feature, causing the server to exhaust available memory and become unavailable to all users.
It is possible to read the advisory at discuss.elastic.co. This vulnerability is known as CVE-2026-63261 since 07/16/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 8.19.19, 9.3.8 or 9.4.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-47589). Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
- 8.19.0
- 8.19.1
- 8.19.2
- 8.19.3
- 8.19.4
- 8.19.5
- 8.19.6
- 8.19.7
- 8.19.8
- 8.19.9
- 8.19.10
- 8.19.11
- 8.19.12
- 8.19.13
- 8.19.14
- 8.19.15
- 8.19.16
- 8.19.17
- 8.19.18
- 9.3.0
- 9.3.1
- 9.3.2
- 9.3.3
- 9.3.4
- 9.3.5
- 9.3.6
- 9.3.7
- 9.4.0
- 9.4.1
- 9.4.2
- 9.4.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Kibana 8.19.19/9.3.8/9.4.4
Timeline
07/16/2026 CVE reserved07/22/2026 Advisory disclosed
07/22/2026 VulDB entry created
07/22/2026 VulDB entry last update
Sources
Advisory: discuss.elastic.coStatus: Confirmed
CVE: CVE-2026-63261 (🔒)
GCVE (CVE): GCVE-0-2026-63261
GCVE (VulDB): GCVE-100-382039
EUVD: 🔒
Entry
Created: 07/22/2026 07:48Updated: 07/22/2026 12:58
Changes: 07/22/2026 07:48 (53), 07/22/2026 12:58 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.