Allocation of Resources Without Limits or Throttling in Elasticsearch can lead to denial of service via a
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 3 Nov 2026, 19:45 UTC
Thin evidence
One scorer or none| CNA (elastic) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ElasticElasticsearch | Affected
| Fixed in– |
AI-suggested
Since the vulnerability requires authenticated access with specific permissions, restricting write and search permissions to trusted users can reduce risk. Monitor vendor advisories for updates and apply any forthcoming patches promptly. Until a fix is available, consider disabling or avoiding use of the affected phonetic encoders if feasible.
Description
A vulnerability in Elasticsearch's analysis-phonetic plugin allows an authenticated user with write or search permissions on an affected index to cause a denial of service. This occurs due to allocation of resources without limits or throttling (CWE-770) when processing specially crafted input values, leading to heap memory exhaustion and potential node unresponsiveness or termination.