# CVE-2026-0528: Improper Input Validation in Metricbeat Leading to Denial of Service > Attackers can cause denial of service in Elastic Metricbeat by sending malformed payloads to Graphite, Zookeeper, or Prometheus metricsets. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Jan 2026 - **Updated:** 13 Jan 2026 - **Also known as:** GHSA-w2gr-585j-r428, GO-2026-4360, MINI-3fhh-fv2x-8hqc, MINI-3hj8-2mr2-v9c8, MINI-3hw6-5m2v-vj79, MINI-4vg4-gj77-x8mj, MINI-8fxr-wvc2-xj9w, MINI-8x5m-8cxm-xf37, MINI-93qx-c8jf-c3w4, MINI-9gg7-7734-rwxw, MINI-gcmp-gvwg-37vc, MINI-h8j2-f6r9-35qq, MINI-j5hf-6x69-ch32, MINI-jhm2-xf77-x329, MINI-jw24-7r3m-x6w2, MINI-pv54-65gv-qvc9, MINI-vvj6-fr95-w8h9, MINI-x88q-qpf7-w8hv ## What is CVE-2026-0528? CVE-2026-0528 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-129 (Improper Validation of Array Index) ## Which versions are affected by CVE-2026-0528? 10 open source packages ship an affected version, including github.com/elastic/beats/v7 and github.com/elastic/beats. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/elastic/beats/v7` | Go | All versions | 7.0.0-alpha2.0.20251217054608-6e42552a23ce | | `github.com/elastic/beats/v7` | Go | All versions | 7.0.0-alpha2.0.20251217054608-6e42552a23ce | | `github.com/elastic/beats/v7` | Go | All versions | 7.0.0-alpha2.0.20251217054608-6e42552a23ce | | `github.com/elastic/beats/v7` | Go | From 8.0.0 | 8.19.10 | | `github.com/elastic/beats/v7` | Go | From 8.0.0 | 8.19.10 | | `github.com/elastic/beats/v7` | Go | From 9.0.0 | 9.1.10 | | `github.com/elastic/beats/v7` | Go | From 9.0.0 | 9.1.10 | | `github.com/elastic/beats/v7` | Go | From 9.2.0 | 9.2.4 | | `github.com/elastic/beats/v7` | Go | From 9.2.0 | 9.2.4 | | `github.com/elastic/beats` | Go | All versions | None | Products: Elastic Kibana. ## How do I fix CVE-2026-0528? Upgrade github.com/elastic/beats/v7 to a fixed version for your release line: 7.0.0-alpha2.0.20251217054608-6e42552a23ce, 8.19.10, 9.1.10 or 9.2.4. ## Is CVE-2026-0528 being exploited? There is no known exploitation of CVE-2026-0528 in the wild and no public exploit code. ## Other vulnerabilities in Elastic Kibana - [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild) - [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9) - [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9) - [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9) - [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-0528 and fix it if it is affected. What it is: CVE-2026-0528 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-0528 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/elastic/beats/v7 (Go): affected all versions; fixed in 7.0.0-alpha2.0.20251217054608-6e42552a23ce - github.com/elastic/beats/v7 (Go): affected all versions; fixed in 7.0.0-alpha2.0.20251217054608-6e42552a23ce - github.com/elastic/beats/v7 (Go): affected all versions; fixed in 7.0.0-alpha2.0.20251217054608-6e42552a23ce - github.com/elastic/beats/v7 (Go): affected from 8.0.0; fixed in 8.19.10 - github.com/elastic/beats/v7 (Go): affected from 8.0.0; fixed in 8.19.10 - github.com/elastic/beats/v7 (Go): affected from 9.0.0; fixed in 9.1.10 - github.com/elastic/beats/v7 (Go): affected from 9.0.0; fixed in 9.1.10 - github.com/elastic/beats/v7 (Go): affected from 9.2.0; fixed in 9.2.4 - github.com/elastic/beats/v7 (Go): affected from 9.2.0; fixed in 9.2.4 - github.com/elastic/beats (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-0528/ (Markdown: https://insights.sbomify.com/CVE-2026-0528/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0528 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0528 - OSV: https://osv.dev/vulnerability/CVE-2026-0528 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-0528/ Summaries are generated and may contain mistakes; the official description above is the record.