# CVE-2026-103007: Incorrect Authorization in Elasticsearch Leading to Privilege Escalation

> Attackers with delegated privileges can escalate to full admin by exploiting flawed index scoping in Elasticsearch role management.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** BIT-elasticsearch-2026-103007, CLEANSTART-2026-PW54741, GHSA-5jrv-cmh5-3vmg, MINI-3crm-4p87-69g9, MINI-5g6c-mq29-mvv6, MINI-5xmf-h63q-9784, MINI-5xxq-x9hr-gwr7, MINI-783v-jqmc-h9p4, MINI-c2f2-r9xp-jf36, MINI-ff3v-9f4f-gx87, MINI-hc33-5jxf-g5vc, MINI-hgw9-g38h-6pj6, MINI-jg9q-4483-gj4c, MINI-m6jq-7qp4-f9qg, MINI-m6xh-9v84-rq72, MINI-pqwc-cp97-g75j, MINI-pxcr-fr6p-hff3, MINI-q5vq-4686-47f6, MINI-qqpv-cwwq-ffxr, MINI-qxrr-8rvm-f7wx, MINI-r8hp-68gc-mm76, MINI-rcvg-92vv-p32f, MINI-w88r-935r-4vr4

## What is CVE-2026-103007?

CVE-2026-103007 is a high-severity vulnerability in Elastic Elasticsearch, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-103007?

1 open source package ship an affected version, including elasticsearch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elasticsearch` | Bitnami | From 8.16.0 | 8.19.22, 9.4.7, 9.5.4 |

Products: Elastic Elasticsearch.

## How do I fix CVE-2026-103007?

Upgrade elasticsearch to a fixed version for your release line: 8.19.22, 9.4.7 or 9.5.4.

## Is CVE-2026-103007 being exploited?

There is no known exploitation of CVE-2026-103007 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Elasticsearch

- [CVE-2015-1427](https://insights.sbomify.com/CVE-2015-1427/): Elasticsearch Groovy Scripting Engine Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2014-3120](https://insights.sbomify.com/CVE-2014-3120/): Elasticsearch Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2015-5377](https://insights.sbomify.com/CVE-2015-5377/): Code injection in n/a (critical 9.8)
- [CVE-2026-72649](https://insights.sbomify.com/CVE-2026-72649/): Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution (high 8.8)
- [CVE-2026-72642](https://insights.sbomify.com/CVE-2026-72642/): Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103007 and fix it if it is affected.

What it is: CVE-2026-103007 is a high-severity vulnerability in Elastic Elasticsearch, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103007 in the wild and no public exploit code.

Affected packages and fixed versions:
- elasticsearch (Bitnami): affected from 8.16.0; fixed in 8.19.22, 9.4.7, 9.5.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103007/ (Markdown: https://insights.sbomify.com/CVE-2026-103007/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103007
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103007
- OSV: https://osv.dev/vulnerability/CVE-2026-103007

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103007/
Summaries are generated and may contain mistakes; the official description above is the record.