Authorization Bypass Through User-Controlled Key in Kibana Leading to Cross-Tenant Data Interception

Summary

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.

Timeline

1. Oct 6, 2026, 7:31 PM UTCCVE published
2. Oct 7, 2026, 12:00 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Oct 8, 2026, 3:55 AM UTCRecord last updated

Affected versions

• 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

• elkBitnami

  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

• kibanaBitnami

  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

References 1