CVE-2026-103007: Elasticsearch vulnerability
Elastic · Elasticsearch
No distribution fix yet for SLES 16.0/16.1, openSUSE Leap 16.0/16.1 · Affected: Elasticsearch · Exploitation: not established
At a glance
Higher than 28% of scored CVEs
What it isNVD
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.
Fix status by distribution
From each distribution’s security tracker. Distributions we did not check are not listed.
- SUSE Linux Enterprise Server 16.1Affected, no fix releasedchecked 20 Nov 22:30 UTC
- SUSE Linux Enterprise Server 16.0Affected, no fix releasedchecked 20 Nov 22:30 UTC
- SUSE Linux Enterprise Server 15 SP7Not affectedchecked 20 Nov 22:30 UTC
- openSUSE Leap 16.1Affected, no fix releasedchecked 20 Nov 22:30 UTC
- openSUSE Leap 16.0Affected, no fix releasedchecked 20 Nov 22:30 UTC
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)
- Not establishedNothing in the sources we check
Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.
Weakness and public checks
- Public check
- No public nuclei template
- Weakness
- Incorrect Authorization · Access Control
Other CVEs in Elasticsearch
Every published CVE for Elastic Elasticsearch, by how far exploitation has gone. This one is among them.
What changed
SUSE status tracked since 6 Nov 2026.
- SUSE’s tracker lists openSUSE Leap 16.0 as affected, with no fix released SUSE
- SUSE’s tracker lists openSUSE Leap 16.1 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP4 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP5 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP6 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP7 as not affected SUSE
- SUSE’s tracker lists SLES 16.0 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 16.1 as affected, with no fix released SUSE
Coverage1 article · 1 outlet
First in our coverage: SecurityOnline, 7 Oct.
- Elastic Patches 14 Flaws as Kibana Fleet Bug Risks Data HijackSecurityOnline · first in our coverage · mentions it in passing
New articles also arrive in the RSS feed.