# CVE-2026-72671: Missing authorization in Kibana

> Attackers with specific job privileges can remove trained models from spaces due to missing authorization checks, requiring a patch.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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-72671, BIT-kibana-2026-72671, GHSA-92c8-vpgp-w44c, MINI-74rm-7r4w-g4rw, MINI-7m7f-c3r3-76j9, MINI-j9f9-g4wq-mhv8, MINI-q2pv-v532-2cqj, MINI-q48w-vqh5-c5jp, MINI-x32g-frwp-rp3j, MINI-xqmr-3mqp-vhpq

## What is CVE-2026-72671?

CVE-2026-72671 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

A Kibana Machine Learning capability that removes a saved object from the current space accepts machine learning trained models as a target, but it verifies only the privileges that apply to anomaly detection jobs and data frame analytics jobs. A user whose role grants create anomaly detection jobs and data frame analytics jobs without the trained model privilege can therefore remove a trained model from a space. The model itself is not deleted and remains available in its other spaces, and the change can be reversed by a suitably privileged user.

Weakness: CWE-862 (Missing Authorization)

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

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-72671?

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

## Is CVE-2026-72671 being exploited?

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

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

## Sources

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

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