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

> An authenticated user can cause a denial of service in Kibana by triggering unbounded resource allocation in the Observability log analysis feature.

- **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-72667, BIT-kibana-2026-72667, GHSA-2qxp-q7cq-6v7x, MINI-7vhq-fwrf-4xvv, MINI-c8wr-4w3j-7jj7, MINI-j6jc-76qh-867v, MINI-p9j7-q3g3-m866, MINI-pfm8-wm79-34h4, MINI-v9cx-rqqr-2fjh, MINI-xxjq-c29w-fr4p

## What is CVE-2026-72667?

CVE-2026-72667 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 specially crafted request submitted by an authenticated user with minimal privileges to a validation capability of the Observability log analysis feature causes Kibana to perform an unbounded amount of concurrent work. This can exhaust the memory available to the Kibana process and make Kibana unavailable to all users until it is restarted. The severity of the outcome depends on the resources allocated to the deployment; on well-provisioned deployments a single request may cause degraded performance and elevated memory pressure rather than a full outage, but the request is inexpensive to repeat.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kibana` | Bitnami | From 8.0.0 | 8.19.20, 9.4.5 |
| `elk` | Bitnami | From 8.0.0 | 8.19.20, 9.4.5 |

Products: Elastic Kibana.

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

Upgrade kibana to a fixed version for your release line: 8.19.20 or 9.4.5.

## Is CVE-2026-72667 being exploited?

There is no known exploitation of CVE-2026-72667 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-72667 and fix it if it is affected.

What it is: CVE-2026-72667 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-72667 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.0.0; fixed in 8.19.20, 9.4.5
- elk (Bitnami): affected from 8.0.0; fixed in 8.19.20, 9.4.5

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-72667/ (Markdown: https://insights.sbomify.com/CVE-2026-72667/index.md)
```

## Sources

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

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