# CVE-2026-102407: Incorrect Authorization in Elasticsearch Leading to Unauthorized Data Stream Modification

> An authenticated user can modify unauthorized data streams in Elasticsearch, potentially injecting data or disrupting search functionality.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** AZL-106715, BIT-elasticsearch-2026-102407, GHSA-5jmx-xm76-wvvg, MINI-272v-9qwj-rpcj, MINI-2xm3-6cfq-25f9, MINI-42vg-fp79-rr39, MINI-57rw-p62q-68q9, MINI-6x6r-r57x-g56f, MINI-73pm-8cvh-mj84, MINI-7p83-8c5m-4rv3, MINI-9x9p-wmfw-q929, MINI-c7pv-6rg9-gq3p, MINI-cfcp-xm9v-j8xj, MINI-f9xg-9c83-jrrm, MINI-fjmj-9x8j-x8qq, MINI-fw5w-3fx4-gc67, MINI-jxrj-v842-h474, MINI-mwh3-mpjg-qcgv, MINI-pj7x-52hw-r6jq, MINI-pjfw-q6c4-44gr, MINI-pvwp-c9xm-8q62, MINI-rrcx-3v45-4r99, MINI-v7mx-8692-7h7r, MINI-v92r-jmw6-j9mw, MINI-wfch-m89m-9254, MINI-wrhv-hrvq-v8r2

## What is CVE-2026-102407?

CVE-2026-102407 is a medium-severity missing authorization vulnerability in Elastic Elasticsearch, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect Authorization (CWE-863) in Elasticsearch can lead to unauthorized data stream modification via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user with sufficient privileges over a single resource could use the Modify Data Streams API to modify a data stream to which they were not otherwise authorized, potentially injecting data into it or affecting its ability to be searched normally. This issue does not allow an attacker to read the contents of a data stream they do not otherwise have access to.

Weakness: CWE-863 (Incorrect Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elasticsearch` | Bitnami | From 7.17.5 | 8.19.19, 9.3.8, 9.4.4 |

Products: Elastic Elasticsearch.

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

Upgrade elasticsearch to a fixed version for your release line: 8.19.19, 9.3.8 or 9.4.4.

## Is CVE-2026-102407 being exploited?

There is no known exploitation of CVE-2026-102407 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-102407 and fix it if it is affected.

What it is: CVE-2026-102407 is a medium-severity missing authorization vulnerability in Elastic Elasticsearch, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102407 in the wild and no public exploit code.

Affected packages and fixed versions:
- elasticsearch (Bitnami): affected from 7.17.5; fixed in 8.19.19, 9.3.8, 9.4.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-102407/ (Markdown: https://insights.sbomify.com/CVE-2026-102407/index.md)
```

## Sources

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

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