Elastic Kibana up to 7.17.29/8.19.9/9.1.9/9.2.3 Bulk allocation of resources

Summaryinfo

A vulnerability identified as critical has been detected in Elastic Kibana up to 7.17.29/8.19.9/9.1.9/9.2.3. Affected by this vulnerability is an unknown functionality of the component Bulk Handler. Performing a manipulation results in allocation of resources. This vulnerability was named CVE-2026-0531. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in Elastic Kibana up to 7.17.29/8.19.9/9.1.9/9.2.3. This affects some unknown functionality of the component Bulk Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana Fleet can lead to Excessive Allocation (CAPEC-130) via a specially crafted bulk retrieval request. This requires an attacker to have low-level privileges equivalent to the viewer role, which grants read access to agent policies. The crafted request can cause the application to perform redundant database retrieval operations that immediately consume memory until the server crashes and becomes unavailable to all users.

It is possible to read the advisory at discuss.elastic.co. This vulnerability is uniquely identified as CVE-2026-0531 since 12/19/2025. The exploitability is told to be easy. It is possible to initiate the attack 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.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-2038). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Elastic

Name

• Kibana

Version

• 7.17.0
• 7.17.1
• 7.17.2
• 7.17.3
• 7.17.4
• 7.17.5
• 7.17.6
• 7.17.7
• 7.17.8
• 7.17.9
• 7.17.10
• 7.17.11
• 7.17.12
• 7.17.13
• 7.17.14
• 7.17.15
• 7.17.16
• 7.17.17
• 7.17.18
• 7.17.19
• 7.17.20
• 7.17.21
• 7.17.22
• 7.17.23
• 7.17.24
• 7.17.25
• 7.17.26
• 7.17.27
• 7.17.28
• 7.17.29
• 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
• 9.1.0
• 9.1.1
• 9.1.2
• 9.1.3
• 9.1.4
• 9.1.5
• 9.1.6
• 9.1.7
• 9.1.8
• 9.1.9
• 9.2.0
• 9.2.1
• 9.2.2
• 9.2.3

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion