Quick answers
- Is CVE-2026-72649 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72649 being exploited in the wild.
- How severe is CVE-2026-72649?
- High severity, with a CVSS score of 8.8, published 1 September 2026.
- Which products and versions are affected?
- Elasticsearch 8.0.0 to 8.19.19, 9.0.0 to 9.4.4, 9.5.0.
- Is there a fix for CVE-2026-72649?
- A patch was published on 2026-09-01: Fixed in Elasticsearch 8.19.20, 9.4.5, and 9.5.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72649 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72649?
- Check whether you run Elasticsearch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a deserialization of untrusted data flaw (CWE-502) in Elasticsearch's machine learning component that enables object injection attacks (CAPEC-586). When a specially crafted trained model artifact is uploaded and deployed, attacker-controlled logic executes with elevated system-call privileges. Exploitation requires network access to an Elasticsearch cluster and valid credentials with sufficient permissions to create, upload, and deploy trained models. An authenticated attacker can achieve remote code execution with the privileges of the Elasticsearch process. Mitigation includes disabling machine learning or upgrading to patched versions 8.19.20, 9.4.5, or 9.5.1.
Affected products
- Elastic Elasticsearch 8.0.0 to 8.19.19, 9.0.0 to 9.4.4, 9.5.0
Timeline
- 2026-09-01: disclosed: CVE-2026-72649 published on NVD and ESA-2026-114 advisory released
- 2026-09-01: patched: Fixed in Elasticsearch 8.19.20, 9.4.5, and 9.5.1