This page lists publicly disclosed CVE vulnerabilities affecting elastic elasticsearch (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-68390 | Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can allow an authenticated user with snapshot restore privileges to cause Excessive Allocation (CAPEC-130) of memory and a denial of service (DoS) via crafted HTTP request. | [email protected] | 4.9 | 0.34% | 2025-12-18 | 2026-06-17 |
| CVE-2025-68384 | Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can allow a low-privileged authenticated user to cause Excessive Allocation (CAPEC-130) causing a persistent denial of service (OOM crash) via submission of oversized user settings data. | [email protected] | 6.5 | 0.24% | 2025-12-18 | 2026-06-17 |
| CVE-2025-37731 | Improper Authentication in Elasticsearch PKI realm can lead to user impersonation via specially crafted client certificates. A malicious actor would need to have such a crafted client certificate signed by a legitimate, trusted Certificate Authority. | [email protected] | 6.8 | 0.16% | 2025-12-15 | 2026-06-17 |
| CVE-2025-37727 | 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 | [email protected] | 5.7 | 0.22% | 2025-10-10 | 2026-06-17 |
| CVE-2024-52979 | Uncontrolled Resource Consumption in Elasticsearch while evaluating specifically crafted search templates with Mustache functions can lead to Denial of Service by causing the Elasticsearch node to crash. | [email protected] | 6.5 | 0.52% | 2025-05-01 | 2026-06-17 |
| CVE-2024-52981 | An issue was discovered in Elasticsearch, where a large recursion using the Well-KnownText formatted string with nested GeometryCollection objects could cause a stackoverflow. | [email protected] | 4.9 | 0.47% | 2025-04-08 | 2026-06-17 |
| CVE-2024-52980 | A flaw was discovered in Elasticsearch, where a large recursion using the innerForbidCircularReferences function of the PatternBank class could cause the Elasticsearch node to crash. A successful attack requires a malicious user to have read_pipeline Elasticsearch cluster privilege assigned to them. | [email protected] | 6.5 | 0.43% | 2025-04-08 | 2026-06-17 |
| CVE-2024-43709 | An allocation of resources without limits or throttling in Elasticsearch can lead to an OutOfMemoryError exception resulting in a crash via a specially crafted query using an SQL function. | [email protected] | 6.5 | 0.57% | 2025-01-21 | 2026-06-17 |
| CVE-2024-12539 | An issue was discovered where improper authorization controls affected certain queries that could allow a malicious actor to circumvent Document Level Security in Elasticsearch and get access to documents that their roles would normally not allow. | [email protected] | 6.0 | 0.37% | 2024-12-17 | 2026-06-17 |
| CVE-2024-23444 | It was discovered by Elastic engineering that when elasticsearch-certutil CLI tool is used with the csr option in order to create a new Certificate Signing Requests, the associated private key that is generated is stored on disk unencrypted even if the --pass parameter is passed in the command invocation. | [email protected] | 4.9 | 0.21% | 2024-07-31 | 2026-06-17 |
| CVE-2023-49921 | An issue was discovered by Elastic whereby Watcher search input logged the search query results on DEBUG log level. This could lead to raw contents of documents stored in Elasticsearch to be printed in logs. Elastic has released 8.11.2 and 7.17.16 that resolves this issue by removing this excessive logging. This issue only affects users that use Watcher and have a Watch defined that uses the search input and additionally have set the search input’s logger to DEBUG or finer, for example using: or | [email protected] | 5.2 | 0.46% | 2024-07-26 | 2026-06-17 |
| CVE-2024-37280 | A flaw was discovered in Elasticsearch, affecting document ingestion when an index template contains a dynamic field mapping of “passthrough” type. Under certain circumstances, ingesting documents in this index would cause a StackOverflow exception to be thrown and ultimately lead to a Denial of Service. Note that passthrough fields is an experimental feature. | [email protected] | 4.9 | 0.53% | 2024-06-13 | 2026-06-17 |
| CVE-2024-23445 | It was identified that if a cross-cluster API key https://www.elastic.co/guide/en/elasticsearch/reference/8.14/security-api-create-cross-cluster-api-key.html#security-api-create-cross-cluster-api-key-request-body restricts search for a given index using the query or the field_security parameter, and the same cross-cluster API key also grants replication for the same index, the search restrictions are not enforced during cross cluster search operations and search results may include documents a | [email protected] | 6.5 | 0.46% | 2024-06-12 | 2026-06-17 |
| CVE-2024-23449 | An uncaught exception in Elasticsearch >= 8.4.0 and < 8.11.1 occurs when an encrypted PDF is passed to an attachment processor through the REST API. The Elasticsearch ingest node that attempts to parse the PDF file will crash. This does not happen with password-protected PDF files or with unencrypted PDF files. | [email protected] | 4.3 | 0.68% | 2024-03-29 | 2026-06-17 |
| CVE-2024-23451 | Incorrect Authorization issue exists in the API key based security model for Remote Cluster Security, which is currently in Beta, in Elasticsearch 8.10.0 and before 8.13.0. This allows a malicious user with a valid API key for a remote cluster configured to use the new Remote Cluster Security to read arbitrary documents from any index on the remote cluster, and only if they use the Elasticsearch custom transport protocol to issue requests with the target index ID, the shard ID and the document I | [email protected] | 4.4 | 0.49% | 2024-03-27 | 2026-06-17 |
| CVE-2024-23450 | A flaw was discovered in Elasticsearch, where processing a document in a deeply nested pipeline on an ingest node could cause the Elasticsearch node to crash. | [email protected] | 4.9 | 0.94% | 2024-03-27 | 2026-06-17 |
| CVE-2023-46674 | An issue was identified that allowed the unsafe deserialization of java objects from hadoop or spark configuration properties that could have been modified by authenticated users. Elastic would like to thank Yakov Shafranovich, with Amazon Web Services for reporting this issue. | [email protected] | 6.0 | 0.24% | 2023-12-05 | 2026-06-17 |
| CVE-2023-46673 | It was identified that malformed scripts used in the script processor of an Ingest Pipeline could cause an Elasticsearch node to crash when calling the Simulate Pipeline API. | [email protected] | 6.5 | 0.84% | 2023-11-22 | 2026-06-17 |
| CVE-2021-37937 | An issue was found with how API keys are created with the Fleet-Server service account. When an API key is created with a service account, it is possible that the API key could be created with higher privileges than intended. Using this vulnerability, a compromised Fleet-Server service account could escalate themselves to a super-user. | [email protected] | 5.9 | 0.71% | 2023-11-21 | 2026-06-17 |
| CVE-2023-31419 | A flaw was discovered in Elasticsearch, affecting the _search API that allowed a specially crafted query string to cause a Stack Overflow and ultimately a Denial of Service. | [email protected] | 6.5 | 60.68% | 2023-10-26 | 2026-06-17 |