dbcve.org
KibanaApplication · Elastic

CVE-2026-0528

HIGH · 7.5 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 7.17.29 / 8.19.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Validation of Array Index (CWE-129) exists in Metricbeat can allow an attacker to cause a Denial of Service through Input Data Manipulation (CAPEC-153) via specially crafted, malformed payloads sent to the Graphite server metricset or Zookeeper server metricset. Additionally, Improper Input Validation (CWE-20) exists in the Prometheus helper module that can allow an attacker to cause a Denial of Service through Input Data Manipulation (CAPEC-153) via specially crafted, malformed metric data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Metricbeat contains input validation flaws in its data ingestion modules. The Graphite server metricset and Zookeeper server metricset fail to properly validate array indices when parsing incoming metric data (CWE-129), allowing out-of-bounds array access that can trigger a denial of service. Similarly, the Prometheus helper module lacks proper input validation (CWE-20) when processing metric data, enabling denial of service via malformed payloads.

MitigationUpdate Metricbeat to the patched version that implements proper array bounds checking in the Graphite and Zookeeper metricsets and adds input validation to the Prometheus helper module. Consider network segmentation to limit exposure of metrics ingestion endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KibanaApplication
Affected:>= 7.0.0, < 7.17.29>= 8.0.0, < 8.19.10>= 9.0.0, < 9.1.10>= 9.2.0, < 9.2.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kibana installation
    Check if Kibana is installed on the system by looking for its installation directory or process (e.g., ps aux | grep kibana, or check common install paths like /opt/kibana, /usr/share/kibana)
    Affected if Kibana is not installed or not running
  2. Determine installed Kibana version
    Run the command to check the Kibana version, typically 'kibana --version' or inspect the 'kibana.yml' version field, or check the package.json in the Kibana installation directory
    Affected if The installed version falls outside all of these ranges: >= 7.0.0 and < 7.17.29; >= 8.0.0 and < 8.19.10; >= 9.0.0 and < 9.1.10; >= 9.2.0 and < 9.2.4
  3. Identify if Metricbeat is in use
    Check if Metricbeat is running as a service or process on the system (e.g., systemctl status metricbeat, ps aux | grep metricbeat)
    Affected if Metricbeat is not installed or not running alongside Kibana
  4. Check if Graphite metricset is enabled
    Inspect the Metricbeat configuration files (usually in /etc/metricbeat/ or /etc/metricbeat/modules.d/) for any enabled graphite module or metricset configuration
    Affected if The Graphite module or metricset is not enabled in the Metricbeat configuration
  5. Check if Zookeeper metricset is enabled
    Inspect the Metricbeat configuration files for any enabled zookeeper module or metricset configuration
    Affected if The Zookeeper module or metricset is not enabled in the Metricbeat configuration
  6. Check if Prometheus helper module is in use
    Inspect Metricbeat configuration for any input or metricset that uses a Prometheus helper module to process metrics
    Affected if No Prometheus-related input or metricset configuration is present in the Metricbeat setup

The environment is affected if Kibana is installed with a version matching the affected ranges AND Metricbeat with Graphite, Zookeeper, or Prometheus modules is enabled and processing incoming metric data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.17.29 / 8.19.10 / 9.1.10 or later
Fixed in 7.17.298.19.109.1.10
Interim mitigation

Update Metricbeat to the patched version that implements proper array bounds checking in the Graphite and Zookeeper metricsets and adds input validation to the Prometheus helper module. Consider network segmentation to limit exposure of metrics ingestion endpoints.

Recommended fix Moderate confidence

Upgrade to Kibana 7.17.29 / 8.19.10 / 9.1.10 / 9.2.4 or later depending on your major version branch

  1. 1. Identify your current Kibana version by checking the Kibana about page or running `bin/kibana --version`
  2. 2. Based on your current major version line, plan upgrade to the minimum fixed version: For 7.x branches upgrade to 7.17.29+, for 8.x upgrade to 8.19.10+, for 9.0.x upgrade to 9.1.10+, for 9.2.x upgrade to 9.2.4+
  3. 3. Review Elastic Kibana upgrade documentation at https://www.elastic.co/guide/en/kibana/current/upgrade.html
  4. 4. Create a backup of your Kibana configuration and data directories
  5. 5. Perform a test upgrade in a non-production environment first
  6. 6. Stop Kibana service
  7. 7. Upgrade Kibana packages using your package manager (e.g., apt, yum, or RPM)
  8. 8. Start Kibana service and verify successful startup
Caveat Review Elastic Stack upgrade notes - minor version upgrades typically have low breaking change risk but check deprecation notices for your specific plugins and custom visualizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kibana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0528 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0528 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data