Skip to main content

Elasticsearch EUVDEUVD-2026-93938

| CVE-2026-103008 MEDIUM
Uncontrolled Recursion (CWE-674)
2026-10-06 security@elastic.co GHSA-j6cv-2j5r-6m5f
6.5
CVSS 3.1 · Vendor: elastic
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain read access to one index
  2. Delivery
    Define scripted runtime field returning nested geometry
  3. Exploit
    Submit search request to node
  4. Execution
    Serialization recurses past stack limit
  5. Impact
    Target node terminates (manual restart may be required)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Recursion depth limits
Exploitation Conditions

Requires an authenticated account with read access to at least one index, and the ability to submit a request defining a scripted runtime field that produces geometry values. The specific vulnerable path is geometry constructed from a script's output, which - unlike text-supplied geometry - is NOT subject to Elasticsearch's nesting-depth limit; text-based geometry is already bounded and not exploitable. Limiting factors: exploitation is impossible for unauthenticated attackers (PR:L), depends on scripting/runtime-fields functionality being usable by the attacker's role, and yields only availability impact (node crash) with no data exposure. Clusters where index-read users are fully trusted or where scripted runtime fields are restricted face substantially lower practical risk.

Impact

This is a moderate-priority availability issue, not a drop-everything emergency. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 6.5) is internally consistent with the description: network-reachable, low attack complexity, requiring low privileges (an authenticated user with read access to one index), no user interaction, and a pure availability impact (node termination) with no confidentiality or integrity loss. The authentication requirement (PR:L) is the single most important mitigating signal - this cannot be triggered by an unauthenticated internet attacker, which meaningfully narrows the threat to users who already hold at least read credentials (insiders, compromised low-privilege accounts, or multi-tenant/self-service query environments). No EPSS score, CISA KEV listing, or SSVC decision data was supplied, and no public exploit is referenced, so exploitation-probability signals are absent rather than conflicting. The aggravating factor is the description's note that affected nodes 'do not recover automatically on all deployments and may require manual intervention,' which raises the real-world operational cost of a single successful request above a transient crash. Net: real but bounded risk - prioritize patching for multi-tenant or externally-queryable Elasticsearch clusters, lower urgency for clusters where all index-read users are fully trusted.

Exploit ScenarioDerived

An authenticated user holding read access to any single index submits a search request that defines a scripted runtime field whose script emits a deeply nested geometry structure. Because script-produced geometry bypasses the nesting-depth limit applied to text geometry, serialization recurses until it exhausts the node's stack space, crashing the targeted node. No public proof-of-concept is referenced, but the attack is low-complexity and requires only a single crafted request over the normal query API.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Denial of service in Elasticsearch allows an authenticated user (CVSS vector PR:L) who holds read access to a single index to crash a node by defining a scripted runtime field whose script output builds a deeply nested geometry value; because serialization of script-generated geometry lacks the nesting-depth limit applied to text-supplied geometry, recursion exhausts the stack and the node terminates, and on some deployments it does not recover without manual intervention. The issue is availability-only (C:N/I:N/A:H, CVSS 6.5) with no data exposure, and no public exploit code was identified at time of analysis. Fixes are released in Elasticsearch 8.19.23, 9.4.8, and 9.5.5 per ESA-2026-198, so this is a moderate-priority patching item rather than an emergency, but clusters that allow untrusted users to read indices while scripting/runtime fields are enabled should treat it as more urgent.

RemediationAI

Upgrade to the vendor-released patch versions from ESA-2026-198: Elasticsearch 8.19.23, 9.4.8, or 9.5.5 (advisory: https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-198/390872). Because exploitation requires an authenticated account with read access to a single index plus the ability to define a scripted runtime field, interim compensating controls should focus on shrinking that privilege surface: tighten index-level read permissions so untrusted or low-privilege roles cannot read arbitrary indices, and restrict runtime-field/scripting capability for those roles - for example by disabling scripting entirely via cluster setting script.allowed_types: none, or by narrowing script.allowed_contexts so runtime-field scripting is not permitted. The trade-off is real: disabling or narrowing scripting breaks legitimate runtime-field pipelines, ingest-time script logic, and other script-dependent search features, and it must be applied cluster-wide, so it is best scoped to the specific script contexts used by runtime fields rather than removed everywhere at once. Additionally, ensure that if a node does terminate from stack exhaustion, operators monitor cluster health and are prepared to restart the affected node manually, since the advisory-referenced behavior indicates the node may not recover automatically on all deployments; there is no indication of a public exploit, so patching can follow a normal maintenance window rather than an emergency change, with the scripting and privilege restrictions standing in until the upgrade completes.

Affected VersionsENISA

Elasticsearch 9.5.0 ≤9.5.4
Elasticsearch 9.0.0 ≤9.4.7
Elasticsearch 8.12.0 ≤8.19.22

Affected Packages

euvd elasticsearch no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-674 (Uncontrolled Recursion) in Elasticsearch's geometry handling path for scripted runtime fields. Elasticsearch already applies a nesting-depth bound when geometry is supplied as text (for example GeoJSON/Well-Known Text parsing), which caps how deeply structured a shape may be; the vulnerable code path instead constructs geometry values from the output of a Painless-style script used by a runtime field, and that constructed structure is neither depth-checked nor bounded before the code recursively walks and serializes it. An attacker with read access to any single index can submit a search or mapping request that defines such a runtime field, supplying a script that emits a deeply nested structure; the recursive build/serialize step then exceeds available stack space, throwing a stack exhaustion error that is not caught safely, and the affected node process terminates rather than failing the request gracefully. The impact is confined to availability within the same security authority (S:U, PR:L), and the attack is network-reachable and low-complexity (AV:N/AC:L) once credentials and index-read privileges exist. Note that no CPE strings were supplied in the input data; affected component identification relies on the vendor advisory ESA-2026-198 referenced at https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-198/390872 (tagged Denial Of Service, Elastic).

Know when Elasticsearch gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (elastic) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 6.5 MEDIUM

Network query API (AV:N), single crafted request (AC:L), needs authenticated read access to an index (PR:L), no interaction, availability-only node crash (A:H; C/I:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Red Hat 6.5 MEDIUM

Primary rating from Vendor (elastic).

CVSS VectorVendor: elastic

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

DescriptionCVE.org

Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to Denial of Service via a specially crafted request that causes the server to construct and process a deeply nested data structure with no bound on recursion depth. Elasticsearch contains an uncontrolled recursion weakness in how it builds and serializes geometry values produced by scripted runtime fields. Unlike geometry supplied as text, which is subject to a nesting-depth limit, geometry constructed from a script's output is not bounded. An authenticated user with read access to a single index can submit a request defining such a field with a script that produces a deeply nested structure. Processing this request recurses past the available stack space, causing the affected node to terminate. The node does not recover automatically on all deployments and may require manual intervention to restore service.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
High
Elasticsearch is a widely deployed enterprise search and logging datastore
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2015-1427 CRITICAL POC
9.8 Feb 17

The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the s

CVE-2014-3120 HIGH POC
8.1 Jul 28

The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execut

CVE-2015-5531 MEDIUM POC
5.0 Aug 17

Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unsp

CVE-2015-3337 MEDIUM POC
4.3 May 01

Directory traversal vulnerability in Elasticsearch before 1.4.5 and 1.5.x before 1.5.2, when a site plugin is enabled, a

CVE-2023-31419 HIGH
7.5 Oct 26

A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause

CVE-2026-82409 HIGH POC
8.4 Sep 23

Maliciously crafted on-chain account names processed by Klever-Go prior to 1.7.20 are spliced into Elasticsearch _bulk r

CVE-2021-22146 HIGH POC
7.5 Jul 21

All versions of Elastic Cloud Enterprise has the Elasticsearch “anonymous” user enabled by default in deployed clusters.

CVE-2021-22145 MEDIUM POC
6.5 Jul 21

A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting. Rated medium severit

CVE-2026-72649 HIGH
8.8 Sep 01

Remote code execution in Elasticsearch's machine learning component allows an authenticated user with ML model deploymen

CVE-2026-72642 HIGH
8.8 Aug 13

Heap corruption and potential remote code execution in Elasticsearch's native ML inference engine can be triggered by an

CVE-2020-7014 HIGH
8.8 Jun 03

The fix for CVE-2020-7009 was found to be incomplete. Rated high severity (CVSS 8.8), this vulnerability is remotely exp

CVE-2020-7009 HIGH
8.8 Mar 31

Elasticsearch versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2 contain a privilege escalation flaw if an attacker

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy