Elasticsearch vulnerabilities and fixes

CVEs that mention Elasticsearch, ranked by priority. 3 tracked.

Elasticsearch has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-08-06. Highest priority: CVE-2026-19111 (score 44/100).

• CVE-2026-19111 HIGH 8.1 Insecure direct object reference in the mongodb_memory, elasticsearch_memory, and mem0_memory tools in Amazon
• CVE-2026-63263 MEDIUM 6.5 UPGRADE Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Exponential Dat
• CVE-2026-63144 MEDIUM 6.5 UPGRADE Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search

FAQ

How do I fix Elasticsearch vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is Elasticsearch being exploited right now?

None of the tracked Elasticsearch CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which Elasticsearch CVE should I patch first?

CVE-2026-19111 currently ranks highest (44/100): Insecure direct object reference in the mongodb_memory, elasticsearch_memory, and mem0_memory tools in Amazon .

← Back to latest CVEs