# CVE-2026-33461: Incorrect Authorization in Kibana Fleet Leading to Information Disclosure

> Users with limited Fleet privileges can access sensitive configuration data, including private keys, via an internal API endpoint.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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:** 8 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** BIT-elk-2026-33461, BIT-kibana-2026-33461, GHSA-jf72-2wmj-p2f3, MINI-2w5v-x4r9-vr6r, MINI-cqrj-r357-g7wf, MINI-cvfc-8f63-5h9f, MINI-grq7-2wwm-9wq3, MINI-qv3j-93vx-hhph, MINI-rwxc-xh2x-gm9f

## What is CVE-2026-33461?

CVE-2026-33461 is a high-severity missing authorization vulnerability in Elastic Kibana, published on 8 Apr 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 information disclosure via Privilege Abuse (CAPEC-122). A user with limited Fleet privileges can exploit an internal API endpoint to retrieve sensitive configuration data, including private keys and authentication tokens, that should only be accessible to users with higher-level settings privileges. The endpoint composes its response by fetching full configuration objects and returning them directly, bypassing the authorization checks enforced by the dedicated settings APIs.

Weakness: CWE-863 (Incorrect Authorization)

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

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.14, 9.2.8, 9.3.3 |
| `elk` | Bitnami | From 8.0.0 | 8.19.14, 9.2.8, 9.3.3 |

Products: Elastic Kibana.

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

Upgrade kibana to a fixed version for your release line: 8.19.14, 9.2.8 or 9.3.3.

## Is CVE-2026-33461 being exploited?

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

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

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.0.0; fixed in 8.19.14, 9.2.8, 9.3.3
- elk (Bitnami): affected from 8.0.0; fixed in 8.19.14, 9.2.8, 9.3.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-33461/ (Markdown: https://insights.sbomify.com/CVE-2026-33461/index.md)
```

## Sources

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

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