# CVE-2026-72672: Incorrect Authorization in Kibana Leading to Disclosure of Elastic Defend Endpoint Event Data

> Authenticated users with Elastic Security privileges can bypass Elasticsearch index restrictions to read sensitive endpoint event data, including credentials.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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-72672, BIT-kibana-2026-72672, GHSA-6c3r-vhrx-4vh9, MINI-4qcx-266x-7m29, MINI-hhq3-426c-5rxv, MINI-p4cc-3793-9r82, MINI-vf35-7qgv-xcjh

## What is CVE-2026-72672?

CVE-2026-72672 is a high-severity missing authorization 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

The Elastic Security capability that suggests existing field values while a user authors endpoint policy artifacts queries Elastic Defend event data with Kibana's internal Elasticsearch account instead of the account of the requesting user. Only Kibana feature privileges are verified, and the caller's Elasticsearch index privileges are not. An authenticated user who holds Elastic Security feature privileges but no read access to the Elastic Defend event indices can therefore retrieve field values from that data, including process command line arguments, which commonly contain tokens, credentials, connection strings, and other sensitive operational detail from protected hosts.

Weakness: CWE-863 (Incorrect Authorization)

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

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.1.0 | 9.4.5 |
| `elk` | Bitnami | From 9.1.0 | 9.4.5 |

Products: Elastic Kibana.

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

Upgrade kibana to 9.4.5 or later.

## Is CVE-2026-72672 being exploited?

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

What it is: CVE-2026-72672 is a high-severity missing authorization 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-72672 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 9.1.0; fixed in 9.4.5
- elk (Bitnami): affected from 9.1.0; fixed in 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-72672/ (Markdown: https://insights.sbomify.com/CVE-2026-72672/index.md)
```

## Sources

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

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