CVE-2026-0528: GO-2026-4360 - Metricbeat affected by multiple denial of service vulnerabilities in github.com/elastic/beats

CVE-2026-0528 · Severity: low · CVSS 3.1 · Published 2026-03-10

Metricbeat affected by multiple denial of service vulnerabilities in github.com/elastic/beats

Technologies: github.com/elastic/beats (Go), github.com/elastic/beats/v7 (Go). Vendors: Go.

Quick answers

Is CVE-2026-0528 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-0528 being exploited in the wild.
How severe is CVE-2026-0528?
Low severity, with a CVSS score of 3.1, published 10 March 2026.
Which products and versions are affected?
github.com/elastic/beats (Go) SEMVER:introduced=0; github.com/elastic/beats/v7 (Go) SEMVER:introduced=0,fixed=7.0.0-alpha2.0.20251217054608-6e42552a23ce.
Is there a fix for CVE-2026-0528?
Yes. github.com/elastic/beats/v7 (Go): upgrade to 7.0.0-alpha2.0.20251217054608-6e42552a23ce or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-0528?
Check whether you run github.com/elastic/beats (Go) or github.com/elastic/beats/v7 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/elastic/beats/v7 (Go): upgrade to 7.0.0-alpha2.0.20251217054608-6e42552a23ce or later
    go get github.com/elastic/beats/v7@v7.0.0-alpha2.0.20251217054608-6e42552a23ce

Affected products

  • github.com/elastic/beats (Go) SEMVER:introduced=0
  • github.com/elastic/beats/v7 (Go) SEMVER:introduced=0,fixed=7.0.0-alpha2.0.20251217054608-6e42552a23ce

Identifiers

  • CVE-2026-0528
  • GHSA-w2gr-585j-r428
  • GO-2026-4360

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.