How severe is CVE-2026-0528?

CVE-2026-0528 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-0528?

CVE-2026-0528 affects the following packages: github.com/elastic/beats/v7 (Go), github.com/elastic/beats/v7 (Go), github.com/elastic/beats/v7 (Go), github.com/elastic/beats/v7 (Go). Ecosystems affected: Go.

How do I fix CVE-2026-0528?

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.

How do I detect CVE-2026-0528 in my Go dependencies?

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.

How do I mitigate CVE-2026-0528 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-0528 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-0528 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-0528?

CVE-2026-0528 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-0528?

CVE-2026-0528 is classified as CWE-129 (CWE-129). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-0528 published, and has it been updated?

CVE-2026-0528 was published on January 13, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2026-0528 — beats

MEDIUMFix: elastic/beats@0025fbf

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

Also known asGHSA-w2gr-585j-r428GO-2026-4360

Published

Jan 13, 2026

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹github.com/elastic/beats/v7🐹github.com/elastic/beats/v7🐹github.com/elastic/beats/v7🐹github.com/elastic/beats/v7

Real-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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/elastic/beats/v7`	all versions	7.0.0-alpha2.0.20251217054608-6e42552a23ce`go 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.10`go get github.com/elastic/beats/v7@v8.19.10`
🐹Go	`github.com/elastic/beats/v7`	≥ 9.0.0&&< 9.1.10	9.1.10`go get github.com/elastic/beats/v7@v9.1.10`
🐹Go	`github.com/elastic/beats/v7`	≥ 9.2.0&&< 9.2.4	9.2.4`go get github.com/elastic/beats/v7@v9.2.4`

Affected Products

1 product · 4 configurations

Application

kibanaelastic

≥ 9.2.0 && < 9.2.4

range

Detection & mitigation playbook

Open-source dependency

Detect
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
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-0528 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-129CWE-129

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 13, 2026

Last updated

Oct 28, 2026

Identifiers

CVE-2026-0528

GHSA-w2gr-585j-r428

GO-2026-4360

References

Advisorygithub.com · CVE 2026 0528.json Advisorynvd.nist.gov · CVE 2026 0528 Webdiscuss.elastic.co Webgithub.com · 0025fbfe668936eb8fa65b838508faf3c3c04387 Webgithub.com · 6e42552a23cec734e7977ebd3eb7fb797ddce456 Webgithub.com · c7664c91a5a68c2df782bfeffe4fb7f42ff2ad1a Packagegithub.com · beats

Related vulnerabilities

Also affects v7

This CVE is medium severity; 5 of 5 other CVEs affecting v7 are rated as high or higher (top: high).

CVE-2026-26933CVE-2026-26931CVE-2025-68383CVE-2025-68388CVE-2023-49922

Same weakness: CWE-129

This CVE is medium severity, in line with the other 3 CVEs with CWE-129.

CVE-2026-116585CVE-2026-115916CVE-2026-116590Browse all CWE-129

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2026-0528 — beats

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-0528 in your dependencies?