# CVE-2026-26931: Memory Allocation with Excessive Size Value in Metricbeat Leading to Denial of Service

> Attackers can cause denial of service in Metricbeat by triggering excessive memory allocation in the Prometheus remote_write handler.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** ECHO-6e6e-7e35-9600, GHSA-5vrw-qjxw-89r5, GO-2026-4790, MINI-3m25-27rr-jm6j, MINI-45vw-48cp-8955, MINI-6p4v-rj56-9f72, MINI-7529-2qf3-7649, MINI-84hh-3vjg-rj56, MINI-92gr-f3hf-v6jm, MINI-9xvg-qq2r-g9vr, MINI-c752-88hq-qqgg, MINI-h63r-82w9-52jh, MINI-h7qj-8pr6-34jx, MINI-hxhc-7q22-fgr8, MINI-pgwc-3qgv-vqcp, MINI-px32-585j-qfph, MINI-rq8g-28g8-5wgq

## What is CVE-2026-26931?

CVE-2026-26931 is a medium-severity denial of service vulnerability in Elastic Metricbeat, published on 19 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory Allocation with Excessive Size Value (CWE-789) in the Prometheus remote_write HTTP handler in Metricbeat can lead Denial of Service via Excessive Allocation (CAPEC-130).

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

## Which versions are affected by CVE-2026-26931?

4 open source packages ship an affected version, including github.com/elastic/beats/v7 and github.com/elastic/beats. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/elastic/beats/v7` | Go | All versions | 7.0.0-alpha2.0.20260112100137-de072c4e371e |
| `github.com/elastic/beats/v7` | Go | All versions | 7.0.0-alpha2.0.20260112100137-de072c4e371e |
| `github.com/elastic/beats/v7` | Go | All versions | 7.0.0-alpha2.0.20260112100137-de072c4e371e |
| `github.com/elastic/beats` | Go | All versions | None |

Products: Elastic Metricbeat.

## How do I fix CVE-2026-26931?

Upgrade github.com/elastic/beats/v7 to 7.0.0-alpha2.0.20260112100137-de072c4e371e or later.

## Is CVE-2026-26931 being exploited?

There is no known exploitation of CVE-2026-26931 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26931 and fix it if it is affected.

What it is: CVE-2026-26931 is a medium-severity denial of service vulnerability in Elastic Metricbeat, published on 19 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26931 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/elastic/beats/v7 (Go): affected all versions; fixed in 7.0.0-alpha2.0.20260112100137-de072c4e371e
- github.com/elastic/beats/v7 (Go): affected all versions; fixed in 7.0.0-alpha2.0.20260112100137-de072c4e371e
- github.com/elastic/beats/v7 (Go): affected all versions; fixed in 7.0.0-alpha2.0.20260112100137-de072c4e371e
- github.com/elastic/beats (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26931/ (Markdown: https://insights.sbomify.com/CVE-2026-26931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26931
- OSV: https://osv.dev/vulnerability/CVE-2026-26931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26931/
Summaries are generated and may contain mistakes; the official description above is the record.