dbcve.org
ElasticsearchDatabase / datastore · Elastic

CVE-2025-37727

MEDIUM · 5.7 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to 8.18.8 / 8.19.5 or later.
See remediation →
59/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Elasticsearch's audit logging for the reindex API can inadvertently capture sensitive information in plain text within log files when auditing is enabled, leading to unauthorized disclosure of confidential data under specific preconditions.

MitigationConfigure Elasticsearch audit settings to filter or exclude sensitive fields from reindex API request logging, or disable audit logging for sensitive endpoints if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElasticsearchDatabase / datastore
Affected:>= 7.0.0, <= 7.17.29>= 8.0.0, < 8.18.8>= 8.19.0, < 8.19.5>= 9.0.0, < 9.0.8>= 9.1.0, < 9.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Elasticsearch version
    Run `curl -XGET 'localhost:9200/'` or check the version from the elasticsearch process logs or package manager
    Affected if The version falls within any of these ranges: 7.0.0-7.17.29, 8.0.0-8.18.7, 8.19.0-8.19.4, 9.0.0-9.0.7, or 9.1.0-9.1.4
  2. Verify if audit logging is enabled
    Check the Elasticsearch configuration file (elasticsearch.yml) for `xpack.security.audit.enabled` set to `true`, or query the cluster settings via `GET /_cluster/settings` looking for audit-related configurations
    Affected if Audit logging is explicitly enabled in the configuration
  3. Confirm the reindex API is accessible
    Check if the reindex API is allowed by verifying index settings or checking for any security policies that might block it. Query `GET /_tasks?actions=*reindex*` to see if reindex operations have been executed
    Affected if The reindex API is accessible and has been used in the environment
  4. Inspect audit log output for sensitive data patterns
    Examine the Elasticsearch audit log directory (commonly in /var/log/elasticsearch/) for entries containing request_body with the reindex action. Look for any plaintext sensitive fields that should have been filtered
    Affected if Audit logs contain unfiltered sensitive information from reindex API requests

A user is affected if they run a vulnerable Elasticsearch version with audit logging enabled and use the reindex API, resulting in unfiltered sensitive data appearing in audit logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.18.8 / 8.19.5 / 9.0.8 or later
Fixed in 8.18.88.19.59.0.8
Interim mitigation

Configure Elasticsearch audit settings to filter or exclude sensitive fields from reindex API request logging, or disable audit logging for sensitive endpoints if not required.

Recommended fix High confidence

Elasticsearch 7.17.30, 8.18.8, 8.19.5, or 9.0.8 (depending on your major version)

  1. 1. Identify the current Elasticsearch version using `GET /` or checking the installation
  2. 2. For Elasticsearch 7.x (7.0.0 to 7.17.29): Upgrade to version 7.17.30 or later
  3. 3. For Elasticsearch 8.x (8.0.0 to 8.18.7): Upgrade to version 8.18.8 or later
  4. 4. For Elasticsearch 8.x (8.19.0 to 8.19.4): Upgrade to version 8.19.5 or later
  5. 5. For Elasticsearch 9.x (9.0.0 to 9.0.7): Upgrade to version 9.0.8 or later
  6. 6. After upgrade, verify the fix by checking release notes and testing reindex API audit logging functionality
  7. 7. Review audit logs from before the patch to identify any exposed sensitive information and rotate any compromised credentials
Caveat Elasticsearch minor version upgrades within the same major version typically have minimal breaking changes; refer to the specific release notes for the target version for any known incompatibilities

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Elasticsearch Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37727 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-37727 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data