# CVE-2026-72661: Missing Authorization in Kibana Leading to Information Disclosure

> Low-privileged Kibana users can read endpoint response action records and content due to missing authorization checks in internal data retrieval.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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-72661, BIT-kibana-2026-72661, GHSA-qpcf-cqfc-xxqq, MINI-gpc7-w773-vhg4, MINI-pr5v-jcm9-jpxg, MINI-qxf2-36qw-9w36, MINI-r3p2-hmj5-qc64, MINI-rx8j-x243-6fx3, MINI-whcx-pm54-c9j8, MINI-wr73-8q69-mjf4

## What is CVE-2026-72661?

CVE-2026-72661 is a medium-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

Missing Authorization (CWE-862) in Kibana can lead to information disclosure via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An internal Kibana data retrieval capability used by Elastic Defend endpoint response actions did not enforce the Security Solution and endpoint privileges that its user-facing equivalents require, and it retrieved data with elevated internal permissions rather than the permissions of the requesting user. As a result, an authenticated low-privileged Kibana user with no Security Solution privileges, endpoint privileges and no Elasticsearch privileges on the underlying data, could read endpoint response action records and the corresponding response content returned by managed hosts.

Weakness: CWE-862 (Missing Authorization)

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

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.12.0 | 8.19.19, 9.3.8, 9.4.4 |
| `elk` | Bitnami | From 8.12.0 | 8.19.19, 9.3.8, 9.4.4 |

Products: Elastic Kibana.

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

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

## Is CVE-2026-72661 being exploited?

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

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

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.12.0; fixed in 8.19.19, 9.3.8, 9.4.4
- elk (Bitnami): affected from 8.12.0; fixed in 8.19.19, 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-72661/ (Markdown: https://insights.sbomify.com/CVE-2026-72661/index.md)
```

## Sources

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

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