GHSA-w2gr-585j-r428 is a medium-severity (CVSS 6.5) CWE-129 vulnerability in github.com/elastic/beats/v7. O3 Security confirms whether GHSA-w2gr-585j-r428 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Metricbeat affected by multiple denial of service vulnerabilities
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-6e42552a23ce |
| 🐹Go | github.com/elastic/beats/v7 | ≥ 8.0.0&&< 8.19.10 | 8.19.10 |
| 🐹Go | github.com/elastic/beats/v7 | ≥ 9.0.0&&< 9.1.10 | 9.1.10 |
| 🐹Go | github.com/elastic/beats/v7 | ≥ 9.2.0&&< 9.2.4 | 9.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-w2gr-585j-r428 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 pinpoints whether GHSA-w2gr-585j-r428 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w2gr-585j-r428. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w2gr-585j-r428 in your dependencies?
O3 detects GHSA-w2gr-585j-r428 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.