# CVE-2026-63145: Incorrect Authorization in Kibana Leading to Machine Learning Audit Log Integrity Compromise

> Low-privileged users can modify Machine Learning audit and notification records for arbitrary jobs due to insufficient authorization checks.

- **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:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** BIT-elk-2026-63145, BIT-kibana-2026-63145, GHSA-q5gv-xxq5-3m7c, MINI-3xv7-5fw5-c7x5, MINI-588q-5hx3-85fm, MINI-7mw9-9hwp-qr97, MINI-f43x-cf87-ggmw, MINI-jv66-w23r-cxcv, MINI-r6wq-xqqw-mg2p, MINI-wqrc-whj9-hjr5

## What is CVE-2026-63145?

CVE-2026-63145 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect Authorization (CWE-863) in Kibana can lead to integrity compromise of Machine Learning audit and notification records via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1).

A vulnerability exists in Kibana's Machine Learning functionality where a Machine Learning management endpoint performs an insufficient authorization check. The endpoint validates only a coarse privilege level but does not verify that the requesting user has access to the specific Machine Learning job or notification resources provided in the request. As a result, a low-privileged user with Machine Learning access in any Kibana space can manipulate Machine Learning audit and notification records for arbitrary jobs—including jobs in other spaces or belonging to other users—by leveraging Kibana's internally elevated credentials to write to restricted Machine Learning system indices that the user cannot access directly.

Weakness: CWE-863 (Incorrect Authorization)

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

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

Products: Elastic Kibana.

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

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

## Is CVE-2026-63145 being exploited?

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

What it is: CVE-2026-63145 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 21 Jul 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-63145 in the wild and no public exploit code.

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

## Sources

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

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