# CVE-2026-49095: Improper Input Validation in Kibana Fleet Leading to Privilege Escalation

> Authenticated Fleet users can escalate privileges by manipulating agent policy configurations to gain unauthorized Elasticsearch access.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 30 May 2026
- **Also known as:** BIT-elk-2026-49095, BIT-kibana-2026-49095, GHSA-p9vc-h7rw-q6hq, MINI-39fw-749w-xrfv, MINI-69c3-wr27-jjq9, MINI-69x3-w9cj-f2xp, MINI-cg65-79g6-m98p, MINI-mp4x-w7x4-7hvf, MINI-r483-qcxw-mxmw, MINI-r4r7-m38f-mg34

## What is CVE-2026-49095?

CVE-2026-49095 is a high-severity vulnerability in Elastic Kibana, published on 28 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Input Validation (CWE-20) in the Kibana Fleet agent policy management feature can lead to privilege escalation. An authenticated user with Fleet management privileges can manipulate agent policy configuration by injecting values into a configuration override mechanism that is not adequately validated. An attacker can cause Elastic Agents to be issued API keys with elevated Elasticsearch privileges, potentially granting unauthorized read and write access to sensitive Elasticsearch security indices beyond what is intended for the Fleet management role.

Weakness: CWE-20 (Improper Input Validation)

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

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.16, 9.3.5, 9.4.2 |
| `elk` | Bitnami | From 8.0.0 | 8.19.16, 9.3.5, 9.4.2 |

Products: Elastic Kibana.

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

Upgrade kibana to a fixed version for your release line: 8.19.16, 9.3.5 or 9.4.2.

## Is CVE-2026-49095 being exploited?

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

What it is: CVE-2026-49095 is a high-severity vulnerability in Elastic Kibana, published on 28 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49095 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.0.0; fixed in 8.19.16, 9.3.5, 9.4.2
- elk (Bitnami): affected from 8.0.0; fixed in 8.19.16, 9.3.5, 9.4.2

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

## Sources

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

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