High severity · published Sep 1, 2026
CVE-2026-72649
Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution
8.8
CVSS
0.9%
EPSS
No
On KEV
Description
Deserialization of Untrusted Data (CWE-502) in the Elasticsearch machine learning component can lead to remote code execution via Object Injection (CAPEC-586). A specially crafted trained model artifact could cause attacker-controlled logic to execute with a materially broader system-call surface than intended. Exploitation requires an authenticated user with sufficient privileges to create and deploy trained models.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.9% · higher than 60% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EL
Elasticsearch · Elastic
8.0.0 through 8.19.19; 9.0.0 through 9.4.4; 9.5.0 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72649
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-72649
Vendor Advisory
https://discuss.elastic.co/t/elasticsearch-8-19-20-9-4-5-9-5-1-security-update-esa-2026-114/390087
More from Elasticsearch
9.8
CVE-2015-1427
The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell…
8.1
CVE-2014-3120
The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source…
9.8
CVE-2015-5377
Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the transport protocol
8.8
CVE-2026-72642
Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process
8.8
CVE-2021-37937
An issue was found with how API keys are created with the Fleet-Server service account