Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain read access to one index
-
DeliveryDefine scripted runtime field returning nested geometry
-
ExploitSubmit search request to node
-
ExecutionSerialization recurses past stack limit
-
ImpactTarget 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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).
Primary rating from Vendor (elastic).
CVSS VectorVendor: elastic
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Elasticsearch
View allThe Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the s
The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execut
Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unsp
Directory traversal vulnerability in Elasticsearch before 1.4.5 and 1.5.x before 1.5.2, when a site plugin is enabled, a
A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause
Maliciously crafted on-chain account names processed by Klever-Go prior to 1.7.20 are spliced into Elasticsearch _bulk r
All versions of Elastic Cloud Enterprise has the Elasticsearch “anonymous” user enabled by default in deployed clusters.
A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting. Rated medium severit
Remote code execution in Elasticsearch's machine learning component allows an authenticated user with ML model deploymen
Heap corruption and potential remote code execution in Elasticsearch's native ML inference engine can be triggered by an
The fix for CVE-2020-7009 was found to be incomplete. Rated high severity (CVSS 8.8), this vulnerability is remotely exp
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
EUVD-2026-93938
GHSA-j6cv-2j5r-6m5f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB