CVE-2026-0528

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.

CVE-2026-0528 has a CVSS score of 6.5 (Medium). The vector is reachable from an adjacent network, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.0.0-alpha2.0.20251217054608-6e42552a23ce, 8.19.10, 9.1.10, 9.2.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-0528? CVE-2026-0528 is a medium-severity security vulnerability in github.com/elastic/beats/v7 (go), affecting versions < 7.0.0-alpha2.0.20251217054608-6e42552a23ce. It is fixed in 7.0.0-alpha2.0.20251217054608-6e42552a23ce, 8.19.10, 9.1.10, 9.2.4.
2. How severe is CVE-2026-0528? CVE-2026-0528 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/elastic/beats/v7 are affected by CVE-2026-0528? github.com/elastic/beats/v7 (go) versions < 7.0.0-alpha2.0.20251217054608-6e42552a23ce is affected.
4. Is there a fix for CVE-2026-0528? Yes. CVE-2026-0528 is fixed in 7.0.0-alpha2.0.20251217054608-6e42552a23ce, 8.19.10, 9.1.10, 9.2.4. Upgrade to this version or later.
5. Is CVE-2026-0528 exploitable, and should I be worried? Whether CVE-2026-0528 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-0528 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-0528?
   • Upgrade github.com/elastic/beats/v7 to 7.0.0-alpha2.0.20251217054608-6e42552a23ce or later
   • Upgrade github.com/elastic/beats/v7 to 8.19.10 or later
   • Upgrade github.com/elastic/beats/v7 to 9.1.10 or later
   • Upgrade github.com/elastic/beats/v7 to 9.2.4 or later