# CVE-2026-26939: Missing Authorization in Kibana Leading to Unauthorized Endpoint Response Action Configuration

> Authenticated attackers with rule management privileges can bypass authorization to configure unauthorized endpoint response actions like host isolation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 19 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-x4hf-rw83-jxhf, MINI-4rcg-v2hf-95p6, MINI-69v5-p335-rg4v, MINI-6x7c-g79v-hh7g, MINI-h9pj-4qmc-7232, MINI-q7xg-gp5r-r2fg, MINI-v47x-m489-cfqv

## What is CVE-2026-26939?

CVE-2026-26939 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 19 Mar 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’s server-side Detection Rule Management can lead to Unauthorized Endpoint Response Action Configuration (host isolation, process termination, and process suspension) via CAPEC-1 (Accessing Functionality Not Properly Constrained by ACLs). This requires an authenticated attacker with rule management privileges.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Elastic Kibana.

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

Apply the vendor's patch.

## Is CVE-2026-26939 being exploited?

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

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

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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