CVE-2025-37727
What it is
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
At a glance
- Exploitability
- Can be exploited from the same network segment with a low-privilege account. High risk of data exposure.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 5.7 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-532 · Secrets in logs
- Record status
- Analyzed
Affected
- Elastic Elasticsearch ≤ 7.17.29
- Elastic Elasticsearch < 8.18.8
- Elastic Elasticsearch < 8.19.5
- Elastic Elasticsearch < 9.0.8
- Elastic Elasticsearch < 9.1.5
Attack profile CVSS 3.1 · 5.7
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-37727.md and follow it. Check whether this project is affected by CVE-2025-37727. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
