CVE-2026-26931

Memory Allocation with Excessive Size Value in Metricbeat Leading to Denial of Service

CVSS 3.1 5.7 MEDIUMEUVD CVSS 3.1 5.7 CVSS 3.1 · [email protected] · Secondary 5.7 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/elastic/beats/v7 7.0.0-alpha2.0.20260112100137-de072c4e371eosv · severity unknownFixed by github.com/elastic/beats/v7 7.0.0-alpha2.0.20260112100137-de072c4e371eKEV status unknown

Original advisory

cve-program · CVE-2026-26931

Published

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).

Read the publisher's advisory

euvd · EUVD-2026-13139

Published

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).

Read the publisher's advisory

nvd · CVE-2026-26931

Published

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).

Read the publisher's advisory

osv · GHSA-5vrw-qjxw-89r5

Published

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).

Read the publisher's advisory

osv · GO-2026-4790

Published

Metricbeat Allocates Memory with Excessive Size Value Leading to Denial of Service in github.com/elastic/beats

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

Advisory history

14 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 12:06:55 UTC