CVE-2026-102406: Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana could lead to cross-tenant data interception.
High CVSS 8.8
- CVE id
- CVE-2026-102406
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Kibana Runtimes and servers |
>= 8.14.0, < 8.19.22 >= 9.0.0, < 9.4.7 >= 9.5.0, < 9.5.4 |
8.19.22, 9.4.7, 9.5.4 |
How to fix it
Upgrade Kibana to the fixed release of the line you run: 8.19.22, 9.4.7, 9.5.4.
- Upgrade Kibana (the kibana image tag or packages) to the patched release, matching your Elasticsearch version.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.