CVE-2026-102406

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>kibana8</name>
	<range><lt>8.19.22</lt></range>
      </package>
      <package>
	<name>kibana91</name>
	<range><lt>8.19.22</lt></range>
      </package>
      <package>
	<name>kibana92</name>
	<range><lt>8.19.22</lt></range>
      </package>
      <package>
	<name>kibana93</name>
	<range><lt>8.19.22</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-102406</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-102406</url>
    </references>
    <dates>
      <discovery>2026-10-06</discovery>
      <entry>2026-10-26</entry>
    </dates>
  </vuln>