# CVE-2026-56147: Missing authorization in Kibana

> Low-privileged users can bypass authorization checks to read, modify, or delete protected case attachments in Kibana.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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-56147, BIT-kibana-2026-56147, GHSA-83mc-f7wh-6hxj, MINI-3gqq-q7p5-qcfm, MINI-762h-h224-357p, MINI-7q5j-5wp5-6j6q, MINI-8jg8-c37m-8wgx, MINI-mqvw-39vv-3wvf, MINI-qcj2-xx2r-cxq5, MINI-v274-vpgg-5hj3

## What is CVE-2026-56147?

CVE-2026-56147 is a high-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

Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized information disclosure and case attachment integrity compromise via Privilege Abuse (CAPEC-122). An inconsistency in Kibana's file access authorization logic allows a low-privileged authenticated user to retrieve, modify, and delete case attachments that belong to feature areas they are not authorized to access. Because the access control check and the resource retrieval use different resolution mechanisms, an authenticated attacker with limited file management permissions can obtain the contents of, modify, or delete protected case attachments — such as those associated with Security Solution cases — without holding the privileges required to access those features.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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.7.0 | 8.19.18, 9.3.7, 9.4.3 |
| `elk` | Bitnami | From 8.7.0 | 8.19.18, 9.3.7, 9.4.3 |

Products: Elastic Kibana.

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

Upgrade kibana to a fixed version for your release line: 8.19.18, 9.3.7 or 9.4.3.

## Is CVE-2026-56147 being exploited?

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

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

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.7.0; fixed in 8.19.18, 9.3.7, 9.4.3
- elk (Bitnami): affected from 8.7.0; fixed in 8.19.18, 9.3.7, 9.4.3

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

## Sources

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

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