# CVE-2026-102406: Authorization Bypass Through User-Controlled Key in Kibana Leading to Cross-Tenant Data Interception > Attackers with Fleet privileges can hijack data streams to intercept and modify other tenants' data in Kibana deployments. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **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:** 6 Oct 2026 - **Updated:** 8 Oct 2026 - **Also known as:** BIT-elk-2026-102406, BIT-kibana-2026-102406, GHSA-gpr2-2mpc-hvf2, MINI-6cwj-pxx8-j4vw, MINI-7724-q964-7ff2, MINI-79g2-vf5w-j7g9, MINI-c2r3-rrqf-56v3, MINI-ffwj-j39j-3mf8, MINI-h836-8gwh-rhxv, MINI-p47j-j522-cpj2, MINI-wmwq-3g63-9w56 ## What is CVE-2026-102406? CVE-2026-102406 is a high-severity missing authorization vulnerability in Elastic Kibana, published on 6 Oct 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 could lead to cross-tenant data interception. In this context, "tenant" refers to a user or team sharing the same Kibana deployment, not a separate Elastic Cloud organization or customer. Kibana's Fleet package installation process allowed a user holding delegated Fleet package-management privileges, without direct Elasticsearch administrative privileges, to claim a data stream identifier already in use by another tenant. Because ownership of that identifier was not verified before Fleet applied the uploaded package's generated index and ingest-pipeline settings to already-existing infrastructure, an attacker could redirect an existing tenant's data stream through infrastructure under their control. This exposed the affected tenant's subsequently ingested data to unauthorized disclosure and modification, and prevented that data from reaching its intended destination. Interception could continue even after the malicious package was removed, requiring separate remediation of the affected infrastructure. Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2026-102406? 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.14.0 | 8.19.22, 9.4.7, 9.5.4 | | `elk` | Bitnami | From 8.14.0 | 8.19.22, 9.4.7, 9.5.4 | Products: Elastic Kibana. ## How do I fix CVE-2026-102406? Upgrade kibana to a fixed version for your release line: 8.19.22, 9.4.7 or 9.5.4. ## Is CVE-2026-102406 being exploited? There is no known exploitation of CVE-2026-102406 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-102406 and fix it if it is affected. What it is: CVE-2026-102406 is a high-severity missing authorization vulnerability in Elastic Kibana, published on 6 Oct 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-102406 in the wild and no public exploit code. Affected packages and fixed versions: - kibana (Bitnami): affected from 8.14.0; fixed in 8.19.22, 9.4.7, 9.5.4 - elk (Bitnami): affected from 8.14.0; fixed in 8.19.22, 9.4.7, 9.5.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-102406/ (Markdown: https://insights.sbomify.com/CVE-2026-102406/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102406 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102406 - OSV: https://osv.dev/vulnerability/CVE-2026-102406 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-102406/ Summaries are generated and may contain mistakes; the official description above is the record.