Elasticsearch: Insertion of Sensitive Information into Log File via reindex API

Why this deserves its current priority

CVSS is 5.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps org.elasticsearch:elasticsearch (maven), org.elasticsearch:elasticsearch (maven), org.elasticsearch:elasticsearch (maven), org.elasticsearch:elasticsearch (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for org.elasticsearch:elasticsearch, org.elasticsearch:elasticsearch, org.elasticsearch:elasticsearch.
2. 2Review the reported fix. Update org.elasticsearch:elasticsearch to 8.18.8; org.elasticsearch:elasticsearch to 8.19.5; org.elasticsearch:elasticsearch to 9.0.8; org.elasticsearch:elasticsearch to 9.1.5; org.elasticsearch.plugin:reindex-client to 8.18.8; org.elasticsearch.plugin:reindex-client to 8.19.5; org.elasticsearch.plugin:reindex-client to 9.0.8; org.elasticsearch.plugin:reindex-client to 9.1.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Oct 10, 2025

   Evidence: source:ghsa:source_dates:source-dates:record

2. Source modified

   Sep 29, 2026

   Evidence: source:ghsa:source_dates:source-dates:record

3. First seen by HOL

   Aug 7, 2026

Sources and claim methodology

• Source referencediscuss.elastic.co
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• NVD vulnerability recordnvd.nist.gov
• Source referenceelastic.co
• GitHub security advisorygithub.com