MediumCVE-2026-72660

    Kibana: Uncaught Exception (CVE-2026-72660)

    Published Sources: BSI

    Share

    What is affected, what to do

    Uncaught Exception (CWE-248), resulting from Improper Input Validation (CWE-20), in Kibana can lead to denial of service via Input Data Manipulation (CAPEC-153). An authenticated user holding only low-privileged access can cause an internal error condition in Kibana by supplying specially crafted data.

    Update kibana to version 8.19.20, Kibana to version 8.19.20.

    Affected
    • Elastic Kibana lte 8.0.0..8.19.19
    • Elastic Kibana lte 9.0.0..9.3.7
    • Elastic Kibana lte 9.4.0..9.4.4

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

    Metrics

    6.5

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    6.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: BSI

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 44.9

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    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
    62.51 Methodology
    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
    6.5 Methodology
    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
    6.5
    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.5 %
    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
    44.9
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    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
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 13 August 2026
    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-248

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    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
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    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

    Uncaught Exception (CWE-248), resulting from Improper Input Validation (CWE-20), in Kibana can lead to denial of service via Input Data Manipulation (CAPEC-153). An authenticated user holding only low-privileged access can cause an internal error condition in Kibana by supplying specially crafted data. The resulting error is raised on an execution path so it propagates as an uncaught exception and terminates the Kibana process. Kibana is unavailable to all users until the service is restarted, and the condition can be triggered repeatedly.

    Source: 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
    Affected versionsFixed in
    ElasticKibana
    • 8.0.0 – ≤ 8.19.19
    • 8.19.0 – ≤ 8.19.19
    • 8.5.0 – ≤ 8.19.19
    • 8.9.0 – ≤ 8.19.18
    • 8.9.0 – ≤ 8.19.19
    • 9.0.0 – ≤ 9.3.7
    • 9.0.0 – ≤ 9.4.3
    • 9.0.0 – ≤ 9.4.4
    • 9.1.0 – ≤ 9.4.4
    • 9.2.0 – ≤ 9.4.4
    • 9.3.0 – ≤ 9.3.7
    • 9.4.0 – ≤ 9.4.3
    • 9.4.0 – ≤ 9.4.4
    • 9.5.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    elastickibana
    • 8.0.0 – < 8.19.20
    • 8.19.0 – < 8.19.20
    • 8.5.0 – < 8.19.20
    • 8.9.0 – < 8.19.19
    • 8.9.0 – < 8.19.20
    • 9.0.0 – < 9.3.8
    • 9.0.0 – < 9.4.4
    • 9.0.0 – < 9.4.5
    • 9.1.0 – < 9.4.5
    • 9.2.0 – < 9.4.5
    • 9.3.0 – < 9.3.8
    • 9.4.0 – < 9.4.4
    • 9.4.0 – < 9.4.5
    • 9.5.0
    • < 8.19.20
    • 8.19.20
    • 8.19.20
    • 8.19.20
    • 8.19.19
    • 8.19.20
    • 9.3.8
    • 9.4.4
    • 9.4.5
    • 9.4.5
    • 9.4.5
    • 9.3.8
    • 9.4.4
    • 9.4.5
    • —
    • 8.19.20
    Open SourceKibana
    • < 8.19.20
    • < 9.3.8
    • < 9.4.5
    • < 9.5.1
    • 8.19.20
    • 9.3.8
    • 9.4.5
    • 9.5.1
    Distribution and container packages (10)

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

    Distribution and container packages
    Affected versionsFixed in
    bitnamikibana
    • 8.0.0
    • 8.19.0
    • 8.5.0
    • 8.9.0
    • 9.0.0
    • 9.1.0
    • 9.2.0
    • 9.3.0
    • 9.4.0
    • 9.5.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    LinuxLinux—
    OtherSonstiges—
    LinuxUNIX—
    WindowsWindows—

    Weakness classes (CWE)

    • CWE-248Uncaught Exception

      Base

      An exception is thrown from a function, but it is not caught.

      Entry at MITRE CWE-248

    References & sources

    Linked CVEs

    Linked CVEs
    HighCVE-2026-72681Missing Authorization in Kibana Leading to Privilege Escalation and Information Disclosure8.8—
    MediumCVE-2026-72680Elastic Kibana: Authorization Bypass Through User-Controlled Key6.5—
    HighCVE-2026-72675Elastic Kibana: Missing Authorization7.1—
    MediumCVE-2026-72674Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service6.5—
    MediumCVE-2026-72673Incorrect Authorization in Kibana Leading to Unauthorized Deletion of Synthetics Private Locations5.4—
    HighCVE-2026-72672Incorrect Authorization in Kibana Leading to Disclosure of Elastic Defend Endpoint Event Data7.7—
    MediumCVE-2026-72671Elastic Kibana: Missing Authorization4.3—
    HighCVE-2026-72670Elastic Kibana: Exposure of Sensitive Information to an Unauthorized Actor7.7—
    HighCVE-2026-72669Missing Authorization in Kibana Leading to Cross-User Information Disclosure and Data Tampering7.6—
    MediumCVE-2026-72667Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service6.5—
    MediumCVE-2026-72666Elastic Kibana: Authorization Bypass Through User-Controlled Key6.8—
    HighCVE-2026-72665Missing Authorization in Kibana Leading to Unauthorized Execution of Host Response Actions8.1—
    MediumCVE-2026-72664Missing Authorization in Kibana Leading to Unauthorized Execution of Endpoint Response Actions6.5—
    MediumCVE-2026-72663Inefficient Algorithmic Complexity in Kibana Leading to Denial of Service6.5—
    MediumCVE-2026-72660Uncaught Exception in Kibana Leading to Denial of Service6.5—
    MediumCVE-2026-72659Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service6.5—
    HighCVE-2026-72658Cross-Site Request Forgery in Kibana Leading to Privilege Escalation7.3—
    MediumCVE-2026-72655Elastic Kibana: Improperly Controlled Modification of Dynamically-Determined Object Attributes4.3—
    MediumCVE-2026-72651Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service6.5—
    MediumCVE-2026-72650Authorization Bypass Through User-Controlled Key in Kibana Leading to Information Disclosure4.3—
    HighCVE-2026-72643Elastic Kibana: Incorrect Authorization7.1—
    HighCVE-2026-72632Observable Discrepancy in Kibana Fleet Leading to Disclosure of Elastic Agent Elasticsearch API Keys7.1—
    MediumCVE-2026-72631Improper Privilege Management in Kibana Fleet Leading to Over-Scoped Elastic Agent API Keys6.5—
    HighCVE-2026-72630Incorrect Authorization in Kibana Fleet Leading to Privilege Escalation7.1—
    Show 1 more CVEs
    Linked CVEs
    HighCVE-2026-72629Elastic Kibana: Authorization Bypass Through User-Controlled Key7.1—
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-72660
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-72660"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-72660.svg?lang=en" alt="CVE-2026-72660 – NEOSEC Intel" height="20"></a>