Elasticsearch vulnerabilities and CVEs
Known vulnerabilities affecting Elasticsearch, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.
4 vulnerabilities tracked.
- 7.5 Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via Serialized Data with Nested Payloads (CAPEC-230).
- 6.5 Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to denial of service via a specially crafted input…
- 4.3 Incorrect Authorization (CWE-863) in Elasticsearch can lead to information disclosure via Accessing Functionality Not Properly Constrained…
- 4.2 Use of Cache Containing Sensitive Information (CWE-524) in Elasticsearch can lead to information disclosure and incorrect search results…
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that Elasticsearch is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other products tracked here
Android Windows 11 version 26H1 Windows 11 Version 25H2 Windows 11 Version 24H2 Windows Server 2025 (Server Core installation) Windows Server 2025 Windows Server 2022 Windows 10 Version 21H2 Red Hat Enterprise Linux 9 Windows Server 2019 (Server Core installation) Windows Server 2019 Windows 10 Version 1809 Windows 10 Version 22H2 n/a Windows Server 2016 (Server Core installation) Windows Server 2016 Windows 10 Version 1607 Red Hat Enterprise Linux 10 Red Hat Enterprise Linux 8 Windows Server 2012 R2 (Server Core installation) Windows Server 2012 R2 Windows Server 2012 Windows Server 2012 (Server Core installation) Apache Airflow