CVE-2026-0528 is a medium-severity (CVSS 6.5) CWE-129 vulnerability in github.com/elastic/beats/v7. A fix is available for github.com/elastic/beats/v7 — see the affected versions and patch details below.
Improper Input Validation in Metricbeat Leading to Denial of Service
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-0528.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-0528 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/elastic/beats/v7🐹github.com/elastic/beats/v7🐹github.com/elastic/beats/v7🐹github.com/elastic/beats/v7Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/elastic/beats/v7 | all versions | 7.0.0-alpha2.0.20251217054608-6e42552a23cego get github.com/elastic/beats/v7@v7.0.0-alpha2.0.20251217054608-6e42552a23ce |
| 🐹Go | github.com/elastic/beats/v7 | ≥ 8.0.0&&< 8.19.10 | 8.19.10go get github.com/elastic/beats/v7@v8.19.10 |
| 🐹Go | github.com/elastic/beats/v7 | ≥ 9.0.0&&< 9.1.10 | 9.1.10go get github.com/elastic/beats/v7@v9.1.10 |
| 🐹Go | github.com/elastic/beats/v7 | ≥ 9.2.0&&< 9.2.4 | 9.2.4go get github.com/elastic/beats/v7@v9.2.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/elastic/beats/v7, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/elastic/beats/v7 to 7.0.0-alpha2.0.20251217054608-6e42552a23ce or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-0528 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-0528 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-0528. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-0528 in your dependencies?
O3 Security finds CVE-2026-0528 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.