HighCVE-2026-102406

    Authorization Bypass Through User-Controlled Key in Kibana Leading to Cross-Tenant Data Interception (CVE-2026-102406)

    Published Last modified Sources: OSV, CVE.org, BSI

    What is affected, what to do

    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.

    Update kibana to version 8.19.22, Kibana to version 8.19.22.

    Affected
    • Elastic Kibana lte 8.14.0..8.19.21
    • Elastic Kibana lte 9.0.0..9.4.6
    • Elastic Kibana lte 9.5.0..9.5.3

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: OSV, CVE.org, BSI

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 25.5

    Show all metrics
    Severity
    High
    Priority score

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    79.19
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.3 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    25.5
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-639

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: OSV (Open Source Vulnerabilities), NVD (NIST), cvelistv5, BSI CSAF, BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    VendorProductAffected versionsFixed in
    ElasticKibana
    • 8.14.0 – ≤ 8.19.21
    • 9.0.0 – ≤ 9.4.6
    • 9.5.0 – ≤ 9.5.3
    • —
    • —
    • —
    elastickibana
    • 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
    Open SourceKibana
    • < 8.19.22
    • < 9.4.0
    • < 9.4.7
    • < 9.4.8
    • < 9.5.4
    • < 9.5.5
    • 8.19.22
    • 9.4.0
    • 9.4.7
    • 9.4.8
    • 9.5.4
    • 9.5.5
    Distribution and container packages (3)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    VendorProductAffected versionsFixed in
    bitnamikibana
    • 8.14.0
    • 9.0.0
    • 9.5.0
    • —
    • —
    • —

    Weakness classes (CWE)

    • CWE-639Authorization Bypass Through User-Controlled Key

      Base

      The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

      Entry at MITRE CWE-639

    References & sources

    Reanalysis & status changes

    Chronological NVD audit events for this CVE — reanalyses, CVSS updates, CPE diffs.

    1. Initial Analysisnvd@nist.gov

      • CPE Configuration: after OR *cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:* versions from (including) 9.0.0 up to (excluding) 9.4.7 *cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.19.22 *cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:* versions from (including) 9.5.0 up to (excluding) 9.5.4
      • Reference Type: after Elastic: https://discuss.elastic.co/t/kibana-8-19-22-9-4-7-9-5-4-security-update-esa-2026-187/390860 Types: Mitigation, Vendor Advisory

    2. CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0

      • SSVC: before {"id":"CVE-2026-102406","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technical…
      • SSVC: after {"id":"CVE-2026-102406","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technical…

    3. New CVE Receivedsecurity@elastic.co

      • Description: after 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.
      • CVSS V3.1: after AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
      • CWE: after CWE-639
      • Affected: after New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/102xxx/CVE-2026-102406.json">CVE-2026-102406</a>

    4. CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0

      • SSVC: after {"id":"CVE-2026-102406","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technical…