Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with index write/search permission
-
DeliveryTarget index using affected phonetic encoder
-
ExploitSubmit crafted input to phonetic encoder
-
ExecutionTrigger unbounded heap allocation (CWE-770)
-
ImpactExhaust node heap and crash/hang node
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires that the optional analysis-phonetic plugin be installed and that a target index be configured to use an affected phonetic encoder - this is not a default Elasticsearch configuration. The attacker must be an authenticated user holding permission to write documents to, or run searches against, that specific index (CVSS PR:L). Given those prerequisites, the crafted input is delivered remotely over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N). Limiting factors: dependence on the non-default phonetic plugin and encoder configuration, plus the requirement for pre-existing authenticated index access, meaningfully narrow the exploitable population below the raw CVSS score; impact is confined to availability (node unresponsiveness or termination). |
| Impact | This is a moderate-severity availability-only issue, not a drop-everything emergency, and the signals are internally consistent. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5) describes a network-reachable, low-complexity attack that nonetheless requires authentication (PR:L) and yields only availability impact - no confidentiality or integrity loss. The vuln.today decision label is 'this_month', indicating a plan-and-patch priority rather than act_now/emergency. There is no CISA KEV listing and no EPSS score supplied, and the single reference is Elastic's own security advisory (ESA-2026-235), not exploit code - so there is no public exploit identified at time of analysis. The practical risk is further bounded because exploitation depends on a non-default configuration: the optional analysis-phonetic plugin must be installed and an index must use an affected phonetic encoder, and the attacker must already hold write-or-search permission on that index. Net assessment: a legitimate but not urgent issue for environments that actually run the phonetic plugin; for the large majority of Elasticsearch deployments that do not install it, real-world exposure is low. EPSS is absent, so probabilistic exploitation likelihood could not be weighed. |
| Exploit ScenarioDerived | An authenticated user who can write documents to or run searches against an index configured with an affected phonetic encoder submits a specially crafted input value. The analysis-phonetic plugin allocates memory for that value without limits (CWE-770), exhausting the node's heap so it becomes unresponsive or terminates. Because the CVSS vector is AV:N/AC:L, the request is remote and low-complexity, but the attacker must first hold valid credentials with index write/search access; no public exploit code was identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Heap exhaustion in Elasticsearch's optional analysis-phonetic plugin allows an authenticated user who can write documents to, or run searches against, an index configured with an affected phonetic encoder to drive a node out of memory until it becomes unresponsive or terminates. The flaw is CWE-770 (allocation of resources without limits or throttling) and is reachable remotely with low complexity and no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5), but only when the non-default plugin is installed and a target index actually uses a vulnerable encoder - prerequisites that substantially narrow the exposed population. Availability is the only impacted property; no public exploit code was identified at time of analysis, and the issue is not on the CISA KEV list, consistent with a this_month remediation priority rather than an emergency response.
RemediationAI
Upgrade to one of the fixed releases named in vendor security update ESA-2026-235 - Elasticsearch 8.19.24, 9.4.9 or 9.5.6 - choosing the branch that matches your deployment, and confirm the mapping against the full advisory at https://discuss.elastic.co/t/elasticsearch-8-19-24-9-4-9-9-5-6-security-update-esa-2026-235/391372 before rolling out. Where upgrading cannot be done immediately, the exploitable surface is the non-default analysis-phonetic plugin combined with indices mapped to an affected encoder: removing the plugin from nodes that do not need phonetic analysis, or reconfiguring affected indices to analyzers that do not use a vulnerable encoder (which requires reindexing and changes search/match behavior for those fields), eliminates the exposure but is disruptive and should be validated in a test cluster first. As a complementary control, restrict write and search privileges on indices that use phonetic encoders to the smallest set of trusted users, since the assessed vector requires an authenticated principal with index access (PR:L); this lowers likelihood but does not remove the flaw. Monitor node heap and circuit-breaker events for anomalous growth tied to phonetic analysis requests as a detection signal while remediation is pending.
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
Elasticsearch performs text analysis through Lucene analyzers, and the analysis-phonetic plugin adds phonetic token filters that transform tokens into sound-alike encodings (for example metaphone or soundex style encoders) at both index time and query time. CWE-770 describes the root cause class here: the affected encoder performs resource allocation driven by the input value without an effective bound or throttle, so a crafted value causes heap consumption disproportionate to the request size. Because analysis runs on the coordinating/data node handling the write or search, the consequence is JVM heap exhaustion on that node, leading to unresponsiveness or process termination - an availability-only impact with no confidentiality or integrity component per the assessed vector. The supplied CPE (cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*) is a wildcard across the product line and therefore does not itself bound the vulnerable range; the version scope is defined by the vendor security update ESA-2026-235. Exposure is conditional on the optional plugin being installed and on an index being mapped with an affected encoder, so default Elasticsearch deployments that do not use phonetic analysis are not in the exploitable configuration.
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
Remote low-complexity request (AV:N/AC:L) but requires an authenticated user with index write/search rights (PR:L); impact is availability-only via heap exhaustion (A:H, C:N/I:N).
Primary rating from Vendor (elastic).
CVSS VectorVendor: elastic
DescriptionCVE.org
Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to denial of service via a specially crafted input value that is processed by an affected phonetic encoder of the analysis-phonetic plugin. An authenticated user with permission to write documents to or run searches against an index that uses an affected encoder can cause an Elasticsearch node to exhaust its heap memory. The node can become unresponsive or terminate.
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-116080
NVD
CVE.org
GitHub PoC
Exploit-DB