cve.bz

CVE-2026-72678 elastic elasticsearch

6.5 mediumEPSS 0.5%

Medium (6.5) in elastic elasticsearch. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
Elasticsearch does not validate a size value taken from a user-supplied input before that value is used to reserve memory for an internal data structure. An authenticated user holding only read privileges can submit a single small crafted request to a product API endpoint that causes the node to attempt an excessively large allocation. The resulting memory exhaustion raises a fatal error that terminates the Elasticsearch node process, causing a denial of service for the affected node and degrading cluster health. The defect is not volumetric, so a single request is sufficient regardless of the heap size configured on the target node.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-72678 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72678?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72678?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72678 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Elasticsearchfrom 8.19.0 through 8.19.19
Elasticsearchfrom 9.4.0 through 9.4.4
Elasticsearch9.5.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

An unvalidated allocation flaw exists in Elasticsearch's API request processing mechanisms. When handling user-supplied size parameters during data structure initialization, Elasticsearch fails to bound memory allocation requests. An authenticated remote user with read-only privileges can submit a single crafted API request, forcing an excessively large heap allocation that triggers an Out-Of-Memory (OOM) fatal error and crashes the node process. This results in service disruption and degraded cluster health, posing a high impact to availability.

Red Hat's mitigation

Restrict API access permissions using Elasticsearch role-based access control (RBAC) so that only trusted users can access read endpoints. Additionally, configure request circuit breakers (`indices.breaker.request.limit`) to enforce strict memory allocation caps per request execution.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-72678.

References

Check your stackJSON