High severity · published Aug 13, 2026
CVE-2026-72642
Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process
8.8
CVSS
0.6%
EPSS
No
On KEV
Description
The native inference process that Elasticsearch uses to evaluate uploaded machine learning models accepts a model operation that computes a memory address from an offset supplied inside the model, without validating that the offset stays within the bounds of the underlying storage. A user with the privileges required to upload and deploy a trained model can craft a model that reads and writes memory outside the intended allocation. The result is heap corruption that crashes the inference process, and, with sufficient control over the heap layout, could allow arbitrary code execution in the context of that process.
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.6% · higher than 49% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EL
Elasticsearch · Elastic
8.19.0 through 8.19.19; 9.4.0 through 9.4.4; 9.5.0 · source: vendor, NVD
Affected product
EL
Elasticsearch
Elastic
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-72649
Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution
8.8
CVE-2021-37937
An issue was found with how API keys are created with the Fleet-Server service account