CVE-2026-102406: Elastic Kibana vulnerability
Elastic · Kibana
Vendor fix available · Affected: Elastic Kibana · Exploitation: not established
At a glance
Higher than 28% of scored CVEs
What it isNVD
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.
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)
- Not establishedNothing in the sources we check
Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.
Weakness and public checks
- Public check
- No public nuclei template
- Weakness
- Insecure Direct Object Reference
Other CVEs in Kibana
Every published CVE for Elastic Kibana, by how far exploitation has gone. This one is among them.
Coverage1 article · 1 outlet
First in our coverage: SecurityOnline, 7 Oct.
- Elastic Patches 14 Flaws as Kibana Fleet Bug Risks Data HijackSecurityOnline · first in our coverage
New articles also arrive in the RSS feed.