# CVE-2026-72674: Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service

> Attackers can cause denial of service in Kibana by sending crafted requests to the RAG Playground, exhausting memory and processing resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** BIT-elk-2026-72674, BIT-kibana-2026-72674, GHSA-jx2m-7cw3-3cf8, MINI-67r3-hq59-jm4c, MINI-grqh-pw9r-c346

## What is CVE-2026-72674?

CVE-2026-72674 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-72674?

2 open source packages ship an affected version, including kibana and elk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kibana` | Bitnami | From 9.3.0 | 9.3.8, 9.4.4 |
| `elk` | Bitnami | From 9.3.0 | 9.3.8, 9.4.4 |

Products: Elastic Kibana.

## How do I fix CVE-2026-72674?

Upgrade kibana to a fixed version for your release line: 9.3.8 or 9.4.4.

## Is CVE-2026-72674 being exploited?

There is no known exploitation of CVE-2026-72674 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72674 and fix it if it is affected.

What it is: CVE-2026-72674 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72674 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 9.3.0; fixed in 9.3.8, 9.4.4
- elk (Bitnami): affected from 9.3.0; fixed in 9.3.8, 9.4.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72674/ (Markdown: https://insights.sbomify.com/CVE-2026-72674/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72674
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72674
- OSV: https://osv.dev/vulnerability/CVE-2026-72674

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72674/
Summaries are generated and may contain mistakes; the official description above is the record.