Skip to content
Heist/ feed
Back to feed
HighFix available

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

Type: advisorySources: OSV

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.

Products
kibana
Affected versions
Not specified
Fixed versions
8.19.22, 9.4.7, 9.5.4
CVEs
CVE-2026-102406
Confirmed fixed CVEs
Not specified
Updated in this feed
30 Oct 2026, 12:12 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 14 Oct 2026, 08:47 UTC

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.

osv:BIT-kibana-2026-102406

kibana

Fixed versions: 8.19.22, 9.4.7, 9.5.4

Complete source record
{
  "id": "a22e10e60899f28cd98fd67e63a54f7a590ce7e472c34689e256fbb9544bc2c0",
  "url": "https://osv.dev/vulnerability/BIT-kibana-2026-102406",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "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.",
    "evidence": "osv:BIT-kibana-2026-102406",
    "products": [
      {
        "name": {
          "value": "kibana",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "8.19.22",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "9.4.7",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "9.5.4",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "BIT-kibana-2026-102406",
      "aliases": [
        "BIT-elk-2026-102406",
        "BIT-kibana-2026-102406",
        "CVE-2026-102406"
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "8.14.0"
                },
                {
                  "fixed": "8.19.22"
                },
                {
                  "introduced": "9.0.0"
                },
                {
                  "fixed": "9.4.7"
                },
                {
                  "introduced": "9.5.0"
                },
                {
                  "fixed": "9.5.4"
                }
              ]
            }
          ],
          "package": {
            "name": "kibana",
            "purl": "pkg:bitnami/kibana",
            "ecosystem": "Bitnami"
          },
          "severity": [
            {
              "type": "CVSS_V3",
              "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
            }
          ],
          "database_specific": {
            "source": "https://github.com/bitnami/vulndb/tree/main/data/kibana/BIT-kibana-2026-102406.json"
          }
        }
      ],
      "modified": "2026-10-14T11:11:16.975015388Z",
      "provider": "osv",
      "references": [
        "https://discuss.elastic.co/t/kibana-8-19-22-9-4-7-9-5-4-security-update-esa-2026-187/390860",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-102406"
      ],
      "provider_metadata": {
        "cpes": [
          "cpe:2.3:a:elasticsearch:kibana:*:*:*:*:*:node.js:*:*"
        ],
        "severity": "High"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-102406",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/database_specific/severity"
  },
  "source_id": "core-osv",
  "document_id": 316264,
  "published_at": "2026-10-14T08:47:48.69+00:00"
}