# CVE-2025-37727: Elasticsearch Insertion of sensitive information in log file

> Attackers can read sensitive data from logs when auditing is enabled for reindex API requests in Elasticsearch.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Oct 2025
- **Updated:** 10 Oct 2025
- **Also known as:** BIT-elasticsearch-2025-37727, CLEANSTART-2026-SU96145, ECHO-5478-882b-e488, GHSA-56r7-h6mw-rcfv, MINI-48j9-8wc9-vhqp, MINI-4m7v-9wm5-v496, MINI-5chx-jh3w-c238, MINI-6cmq-hqpw-f3r3, MINI-6qhr-63mj-8h6q, MINI-6xv5-pw3x-f8cc, MINI-9rmq-6842-753r, MINI-9w34-mj23-vcg4, MINI-cjrr-cvr6-4fqw, MINI-m2f4-2vjw-xx58, MINI-m6mj-xqr5-4mv2, MINI-rp7v-7jhc-jfh4, MINI-v3pc-w34j-vg5w, MINI-vpg5-4gp9-qxpp, MINI-wh46-27g8-c3jp, ROOT-APP-MAVEN-CVE-2025-37727, UBUNTU-CVE-2025-37727

## What is CVE-2025-37727?

CVE-2025-37727 is a medium-severity vulnerability in Elastic Elasticsearch, published on 10 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insertion of sensitive information in log file in Elasticsearch can lead to loss of confidentiality under specific preconditions when auditing requests to the  reindex API https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-reindex

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-37727?

9 open source packages ship an affected version, including org.elasticsearch.plugin:reindex-client and elasticsearch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 7.0.0 | 8.18.8 |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 7.0.0 | 8.18.8 |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 8.19.0 | 8.19.5 |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 8.19.0 | 8.19.5 |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 9.0.0-beta1 | 9.0.8 |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 9.0.0-beta1 | 9.0.8 |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 9.1.0 | 9.1.5 |
| `org.elasticsearch.plugin:reindex-client` | Maven | From 9.1.0 | 9.1.5 |
| `elasticsearch` | Bitnami | All versions | 8.18.8, 8.19.5, 9.0.8, 9.1.5 |

Products: Elastic Elasticsearch.

## How do I fix CVE-2025-37727?

Upgrade org.elasticsearch.plugin:reindex-client to a fixed version for your release line: 8.18.8, 8.19.5, 9.0.8 or 9.1.5.

## Is CVE-2025-37727 being exploited?

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

What it is: CVE-2025-37727 is a medium-severity vulnerability in Elastic Elasticsearch, published on 10 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-37727 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.elasticsearch.plugin:reindex-client (Maven): affected from 7.0.0; fixed in 8.18.8
- org.elasticsearch.plugin:reindex-client (Maven): affected from 7.0.0; fixed in 8.18.8
- org.elasticsearch.plugin:reindex-client (Maven): affected from 8.19.0; fixed in 8.19.5
- org.elasticsearch.plugin:reindex-client (Maven): affected from 8.19.0; fixed in 8.19.5
- org.elasticsearch.plugin:reindex-client (Maven): affected from 9.0.0-beta1; fixed in 9.0.8
- org.elasticsearch.plugin:reindex-client (Maven): affected from 9.0.0-beta1; fixed in 9.0.8
- org.elasticsearch.plugin:reindex-client (Maven): affected from 9.1.0; fixed in 9.1.5
- org.elasticsearch.plugin:reindex-client (Maven): affected from 9.1.0; fixed in 9.1.5
- elasticsearch (Bitnami): affected all versions; fixed in 8.18.8, 8.19.5, 9.0.8, 9.1.5

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-2025-37727/ (Markdown: https://insights.sbomify.com/CVE-2025-37727/index.md)
```

## Sources

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

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