Elasticsearch: code execution
High8.8CVE-2026-72642 · Published Aug 13, 2026 · updated Sep 1, 2026
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.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Elasticsearch Product | >= 8.19.0, <= 8.19.19 | No fix yet |
| >= 9.4.0, <= 9.4.4 | No fix yet | |
| <= 9.5.0 | No fix yet |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Severity from
- the vendor (its own CVE record or advisory)
- Weakness
- CWE-823
More Elastic advisories
All Elastic| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Aug 13 | Elasticsearch: denial of service | Medium6.5 | No fix yet |
| Aug 13 | A flaw in Elasticsearch | Medium4.3 | No fix yet |
| Aug 13 | Elasticsearch: denial of service | Medium6.5 | No fix yet |
| Aug 13 | Elasticsearch: denial of service | Medium6.5 | No fix yet |
| Aug 13 | Elastic Kibana: denial of service | Medium6.5 | No fix yet |
| Aug 13 | Elastic Kibana: missing authorization | High7.1 | No fix yet |