cve.bz

CVE-2026-103005 elastic elasticsearch

6.5 mediumEPSS 0.3%

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

On this page
Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user with connector management privileges could cause the cluster to allocate an uncontrolled amount of memory when connector resources with an excessively large `description` field are created and subsequently accessed, exhausting available heap memory and crashing the affected 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.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-17. 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-10-06. 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-103005 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103005?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103005?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-103005 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.12.0 through 8.19.22
Elasticsearchfrom 9.0.0 through 9.3.8
Elasticsearchfrom 9.4.0 through 9.4.7
Elasticsearchfrom 9.5.0 through 9.5.4

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate rather than Important because exploitation requires valid credentials with specific connector management privileges, substantially constraining the attack surface to trusted operators. In typical Red Hat deployments, Elasticsearch endpoints are isolated within protected network segments and administrative privileges are tightly controlled via role-based authorization. Consequently, unauthenticated or unprivileged users cannot trigger the memory exhaustion condition, and the impact is confined to service availability on the affected node.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat Quay 3quay/quay-rhel8Not affected
Red Hat Quay 3quay/quay-rhel9Not affected

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

References

Check your stackJSON