CVE-2026-72642: 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,...

High CVSS 8.8

CVE id
CVE-2026-72642
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Elasticsearch
Runtimes and servers
>= 8.19.0, < 8.19.20
>= 9.4.0, < 9.4.5
>= 9.5.0, < 9.5.1
8.19.20, 9.4.5, 9.5.1

How to fix it

Upgrade Elasticsearch to the fixed release of the line you run: 8.19.20, 9.4.5, 9.5.1.

curl -s localhost:9200
  • Upgrade Elasticsearch (the elasticsearch image tag or packages) to the patched release with a rolling restart; on Elastic Cloud, upgrade the deployment.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.