# CVE-2026-56144: Incorrect Authorization in Elasticsearch Leading to Information Disclosure

> Authenticated users with limited privileges can bypass authorization checks in the ingest simulation feature to read data and metadata from unauthorized indices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 21 Jul 2026
- **Updated:** 26 Aug 2026
- **Also known as:** BIT-elasticsearch-2026-56144, CLEANSTART-2026-GB20617, GHSA-9fhm-53xw-h9c3, MINI-2xv6-hw46-48x7, MINI-3f99-qfxm-4fh9, MINI-5582-fw7w-xf78, MINI-6733-gwv9-ccgw, MINI-6f8r-r8xm-j2j6, MINI-7675-r43r-p7wh, MINI-cf2f-r2m3-q62g, MINI-cpgv-2mmq-9pg4, MINI-fwcp-x83r-cq9v, MINI-jc35-fpxm-93xg, MINI-jrwp-8hwq-w3cv, MINI-p4vx-ghxf-jxwg, MINI-pc8c-4f95-pv2j, MINI-qgr3-v5j2-mpgq, MINI-r7r5-rjm6-4532, MINI-rp4x-98mf-qmm7, MINI-w26c-2w92-862j, MINI-w842-jh74-6x34, MINI-x2q3-285v-hgx6, MINI-x52v-63m7-vxpm, MINI-x89f-3g89-7h85, MINI-xv8x-53f7-m32v

## What is CVE-2026-56144?

CVE-2026-56144 is a medium-severity missing authorization vulnerability in Elastic Elasticsearch, published on 21 Jul 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 allow an authenticated user with limited index privileges to exploit insufficient authorization controls in the ingest simulation feature. By targeting indices they are not authorized to access directly, the user can cause those indices' configured ingest pipelines to execute and return their output, potentially disclosing data processed or enriched by those pipelines. Additionally, the same feature can be used to retrieve index mapping metadata for indices the user are not authorized to access directly.

Weakness: CWE-863 (Incorrect Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elasticsearch` | Bitnami | From 8.12.0 | 8.19.18, 9.3.7, 9.4.4 |

Products: Elastic Elasticsearch.

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

Upgrade elasticsearch to a fixed version for your release line: 8.19.18, 9.3.7 or 9.4.4.

## Is CVE-2026-56144 being exploited?

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

What it is: CVE-2026-56144 is a medium-severity missing authorization vulnerability in Elastic Elasticsearch, published on 21 Jul 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-56144 in the wild and no public exploit code.

Affected packages and fixed versions:
- elasticsearch (Bitnami): affected from 8.12.0; fixed in 8.19.18, 9.3.7, 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-56144/ (Markdown: https://insights.sbomify.com/CVE-2026-56144/index.md)
```

## Sources

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

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