CVSS 3.1
7.2 highCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HHigh (7.2) in elastic elasticsearch. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-103007 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103007?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103007?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103007 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Elasticsearch | from 8.16.0 through 8.19.21 |
| Elasticsearch | from 9.0.0 through 9.4.6 |
| Elasticsearch | from 9.5.0 through 9.5.3 |
Red Hat rates this Important.
An IMPORTANT severity incorrect authorization flaw was found in Elasticsearch. The issue affects deployments that use the configurable, non-default delegated role-management privilege, which 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, so an authenticated user holding this delegated privilege with a broadly-scoped index pattern (for example wildcards or regular expressions that can match restricted or system indices) can update their own assigned role to gain access to indices that should remain restricted, including internal security data, potentially escalating to full administrative control of the cluster. Deployments that do not use this feature, or that scope the privilege only to literal index names, are not affected. The Red Hat CVSS score (7.2, CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) is the same as the upstream Elastic score, and no Red Hat-branded products are affected; the affected scope is limited to community Elasticsearch-related packages in Fedora and EPEL, for which the fix is being pursued through the upstream community process (DELEGATED).
For deployments that use the delegated role-management privilege, review all roles that grant it and ensure their configured index names do not use wildcard or regular-expression patterns that could match system or restricted indices; restrict such grants to literal index names, or remove the privilege from roles assigned to users who should not be able to expand their own access. Audit existing roles created through this feature for unexpected access to restricted or internal indices, and review security audit logs for role or user modifications performed by accounts holding this privilege. Upstream has fixed the issue in Elasticsearch 8.19.22, 9.4.7, and 9.5.4, and upgrading to one of these or a later release verified to contain the fix is recommended. For the affected Fedora and EPEL community packages, apply updated packages once the community provides builds containing the upstream fix.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-feature-server-rhel9 | Affected | |
| Red Hat Quay 3 | quay/quay-rhel8 | Not affected | |
| Red Hat Quay 3 | quay/quay-rhel9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103007.