Skip to content
Fencer Intel
high 8.8

CVE-2026-102406 json

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

published last mo. modified 26d ago also BIT-elk-2026-102406 , BIT-kibana-2026-102406 , EUVD-2026-93927

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

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.

Patch / fix

  • bitnami elk 8.19.22, 9.4.7, 9.5.4
  • bitnami kibana 8.19.22, 9.4.7, 9.5.4
  • elastic kibana 8.19.22, 9.4.7, 9.5.4
  • elasticsearch kibana 8.19.22, 9.4.7, 9.5.4

Is CVE-2026-102406 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami elk
>=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
bitnami kibana
>=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

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.