Kibana authorization bypass lets users intercept other tenants' data
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
Versions 8.14.0 through 8.19.21, 9.0.0 through 9.4.6 and 9.5.0 through 9.5.3 of Elastic Kibana are affected. Fleet does not verify ownership of a data stream identifier (CWE-639) before applying a package to existing infrastructure, so a user with delegated Fleet package-management privileges can claim an identifier used by another tenant. That user can redirect the other tenant's data stream through infrastructure they control, exposing later data to disclosure and modification.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Elastic | Kibana | 8.14.0 – 8.19.21; 9.0.0 – 9.4.6; 9.5.0 – 9.5.3 | — | No fix listed | CNA |
- Kibana VendorElastic Affected 8.14.0 – 8.19.21; 9.0.0 – 9.4.6; 9.5.0 – 9.5.3 Fixed in — No fix listed CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:* | 8.14.0 to before 8.19.22; 9.0.0 to before 9.4.7; 9.5.0 to before 9.5.4 | Vulnerable | Elastic |
- cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:* Versions 8.14.0 to before 8.19.22; 9.0.0 to before 9.4.7; 9.5.0 to before 9.5.4 Vulnerable ·Elastic
Remediation
The sources list no fixed version for Kibana.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Timeline
- 2026-10-06 Threatist record created from CVE-2026-102406
- 2026-10-07 CISA SSVC decision points changed
- 2026-10-07 Priority changed: MEDIUM → LOW
- 2026-10-07 Alias added: GHSA-gpr2-2mpc-hvf2
- 2026-10-07 Priority changed: LOW → MEDIUM
- 2026-10-08 CISA SSVC decision points changed
References
More Elastic Kibana vulnerabilities
- TI-2019-05363 Code injection in Elastic Kibana KEVCVSS 3.1CRITICAL 10.0
- TI-2018-12328 Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the… CVSS 3.0CRITICAL 9.8
- TI-2025-18692 Kibana arbitrary code execution via prototype pollution CVSS 3.1CRITICAL 9.8
- TI-2020-05660 Code injection in Elastic Kibana CVSS 3.1HIGH 8.8
- TI-2024-24803 Deserialization of untrusted data in Elastic Kibana CVSS 3.1CRITICAL 9.9
- TI-2024-24800 Kibana arbitrary code execution via YAML deserialization CVSS 3.1CRITICAL 9.1
Sources
- CVE-2026-102406 · CVE Program
- CVE-2026-102406 · NVD
- FIRST EPSS
- GHSA-gpr2-2mpc-hvf2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences