CVE-2026-26931: Memory Allocation with Excessive Size Value in Metricbeat Leading to Denial of Service
Published Mar 19, 2026
·Updated
Memory Allocation with Excessive Size Value (CWE-789) in the Prometheus remotewrite HTTP handler in Metricbeat can lead Denial of Service via Excessive Allocation (CAPEC-130).
Affected Software
2 affected componentsFixes available
Elastic Metricbeat
go/github.com/elastic/beats/v7<7.0.0-alpha2.0.20260112100137-de072c4e371e
7.0.0-alpha2.0.20260112100137-de072c4e371e
Event History
Mar 19, 2026
CVE Published
via MITRE·05:05 PM
Data Sourced
via MITRE·05:05 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-26931?
CVE-2026-26931 is classified as a Denial of Service vulnerability due to excessive memory allocation.
2
How do I fix CVE-2026-26931?
To fix CVE-2026-26931, update to the latest version of Elastic Metricbeat that addresses the vulnerability.
3
What affects CVE-2026-26931?
CVE-2026-26931 affects the Prometheus remote_write HTTP handler in Elastic Metricbeat.
4
What is the risk of CVE-2026-26931?
The risk of CVE-2026-26931 is that it can lead to service outages due to excessive allocation of memory.
5
Is CVE-2026-26931 being actively exploited?
As of now, there are no public reports indicating that CVE-2026-26931 is actively exploited in the wild.