Skip to content
Fencer Intel
high 7.2

CVE-2026-103007 json

Incorrect Authorization in Elasticsearch Leading to Privilege Escalation

published last mo. modified 26d ago also BIT-elasticsearch-2026-103007 , EUVD-2026-93937

cvss
7.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami elasticsearch 8.19.22, 9.4.7, 9.5.4
  • elasticsearch elasticsearch 8.19.22, 9.4.7, 9.5.4
  • elastic elasticsearch 8.19.22, 9.4.7, 9.5.4
  • org.elasticsearch elasticsearch 8.19.22, 9.4.7, 9.5.4

Is CVE-2026-103007 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-103007 updated cvss 7.2

elasticsearch: Elasticsearch: Privilege escalation via improper enforcement of delegated role permissions

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-feature-server-rhel9
    affected: workaround, no fix available
  • Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami elasticsearch
>=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

Affected products

  • Elastic Elasticsearch

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.