Skip to main content

Elasticsearch CVE-2026-63144

| EUVDEUVD-2026-47583 MEDIUM
Uncontrolled Recursion (CWE-674)
2026-07-21 security@elastic.co GHSA-5v5g-hvw6-x2x7
6.5
CVSS 3.1 · Vendor: elastic
Share

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

PR:L reflects mandatory read-level authentication; A:H captures node crash; C and I are N as there is no data access or modification impact.

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

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

Lifecycle Timeline

2
Analysis Generated
Jul 22, 2026 - 07:59 vuln.today
CVE Published
Jul 21, 2026 - 23:18 cve.org
MEDIUM 6.5

DescriptionCVE.org

Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search request submitted by a low-privileged authenticated user. A user with read-level index access can submit a request that triggers unbounded recursive processing within the Elasticsearch query evaluation component, causing a fatal error that terminates the affected node. In single-node deployments, this results in complete service outage; in multi-node clusters, it causes repeated node restarts and sustained availability degradation.

AnalysisAI

Uncontrolled recursion in Elasticsearch's query evaluation component allows a low-privileged authenticated user with read-level index access to crash an affected node by submitting a specially crafted search request. All three active release lines are affected: 8.19.x through 8.19.18, 9.3.x through 9.3.7, and 9.4.x through 9.4.3. The impact ranges from complete service outage in single-node deployments to sustained availability degradation and repeated node restarts in multi-node clusters. No public exploit code or active exploitation has been identified at time of analysis; Elastic has released patched versions 8.19.19, 9.3.8, and 9.4.4.

Technical ContextAI

Elasticsearch is a distributed search and analytics engine built on Apache Lucene. CWE-674 (Uncontrolled Recursion) describes a failure to impose depth or iteration limits on recursive logic, allowing input to drive call-stack growth until a fatal stack overflow or equivalent runtime error terminates the process. In this case, the vulnerable component is the query evaluation path: Elasticsearch's search layer processes user-submitted query DSL structures, and a specially crafted query can trigger recursive evaluation logic that lacks a depth bound. Because Elasticsearch nodes operate as JVM processes, unbounded recursion produces a fatal error that kills the JVM, requiring a node restart. The CVSS vector AV:N/AC:L/PR:L confirms the vulnerability is remotely exploitable at low complexity, requiring only read-level (index-level) authentication - no elevated privileges or specific index configuration beyond basic access is needed.

RemediationAI

Upgrade to Elasticsearch 8.19.19 (for 8.19.x deployments), 9.3.8 (for 9.3.x deployments), or 9.4.4 (for 9.4.x deployments) per the Elastic security advisory ESA-2026-68 at https://discuss.elastic.co/t/elasticsearch-8-19-19-9-3-8-9-4-4-security-update-esa-2026-68/388571. If immediate patching is not possible, restrict search API access at the network layer to trusted internal hosts or authenticated services only, reducing exposure from broadly distributed read credentials. Additionally, audit and tighten index-level privilege grants - revoke read access for accounts that do not require it, minimizing the population of users capable of triggering this path. Note that restricting API access may impact legitimate search clients and monitoring integrations; coordinate with application owners before applying network-layer controls.

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

CVE-2018-3831 HIGH
8.8 Sep 19

Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secre

Share

CVE-2026-63144 vulnerability details – vuln.today

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