Elastic Elasticsearch up to 8.19.16/9.3.5/9.4.2 Machine allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Elastic Elasticsearch up to 8.19.16/9.3.5/9.4.2. Impacted is an unknown function of the component Machine Handler. Such manipulation leads to allocation of resources. This vulnerability is traded as CVE-2026-56149. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Elastic Elasticsearch up to 8.19.16/9.3.5/9.4.2. Affected by this issue is an unknown part of the component Machine Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. CVE summarizes:
Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted machine learning request that causes excessive memory consumption, which may render the affected node unavailable.
The advisory is shared for download at discuss.elastic.co. This vulnerability is handled as CVE-2026-56149 since 06/19/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are needed for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 8.19.0
- 8.19.1
- 8.19.2
- 8.19.3
- 8.19.4
- 8.19.5
- 8.19.6
- 8.19.7
- 8.19.8
- 8.19.9
- 8.19.10
- 8.19.11
- 8.19.12
- 8.19.13
- 8.19.14
- 8.19.15
- 8.19.16
- 9.3.0
- 9.3.1
- 9.3.2
- 9.3.3
- 9.3.4
- 9.3.5
- 9.4.0
- 9.4.1
- 9.4.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.8
VulDB Base Score: 2.7
VulDB Temp Score: 2.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.9
CNA Vector (elastic): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/19/2026 CVE reserved07/01/2026 Advisory disclosed
07/01/2026 VulDB entry created
07/01/2026 VulDB entry last update
Sources
Advisory: discuss.elastic.coStatus: Confirmed
CVE: CVE-2026-56149 (🔒)
GCVE (CVE): GCVE-0-2026-56149
GCVE (VulDB): GCVE-100-375644
Entry
Created: 07/01/2026 20:13Changes: 07/01/2026 20:13 (61)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.