Elastic Kibana up to 9.3.7/9.4.3 Playground for RAG feature allocation of resources

Summaryinfo

A vulnerability classified as problematic has been found in Elastic Kibana up to 9.3.7/9.4.3. This vulnerability affects unknown code of the component Playground for RAG feature. The manipulation leads to allocation of resources. This vulnerability is listed as CVE-2026-72674. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Elastic Kibana up to 9.3.7/9.4.3. It has been rated as problematic. This issue affects some unknown processing of the component Playground for RAG feature. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). A user-supplied list of document fields accepted by the Kibana Playground for RAG feature was neither bounded in length nor de-duplicated before it was used to assemble the response for each matching document. A single crafted request could therefore make Kibana build a response far larger than the data it was derived from, and the resulting processing and memory pressure exhausts the resources of the Kibana instance.

It is possible to read the advisory at discuss.elastic.co. The identification of this vulnerability is CVE-2026-72674 since 08/10/2026. The exploitation is known to be easy. The attack may be initiated 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-58261). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Elastic

Name

• Kibana

Version

• 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

• 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