CVE-2026-103007: Incorrect Authorization (CWE-863) in Elasticsearch can lead to Privilege Escalation via a delegated administrative privilege whose scope is not fully enforced during authorization checks.

High CVSS 7.2

CVE id
CVE-2026-103007
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Elasticsearch
Runtimes and servers
>= 8.16.0, < 8.19.22
>= 9.0.0, < 9.4.7
>= 9.5.0, < 9.5.4
8.19.22, 9.4.7, 9.5.4

How to fix it

Upgrade Elasticsearch to the fixed release of the line you run: 8.19.22, 9.4.7, 9.5.4.

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

Incorrect Authorization (CWE-863) in Elasticsearch can lead to Privilege Escalation via a delegated administrative privilege whose scope is not fully enforced during authorization checks. Elasticsearch contains an incorrect authorization weakness in a configurable, non-default privilege that lets an administrator delegate limited role-management capability to another user, scoped to specific indices. The authorization check that enforces this scoping does not correctly account for a role-definition setting that can expand the matched index set. A user holding this delegated privilege with a broadly-scoped index pattern can exploit this inconsistency by updating their own assigned role to gain access to indices that should remain restricted, including internal security data. This can enable further escalation up to full administrative control of the cluster.

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.