What it is
Search/index engines like Elasticsearch or OpenSearch.
Why it is risky
An unauthenticated cluster on the internet exposes all indices to read/delete and can lead to script execution.
What to do
Enable the security plugin/auth and restrict HTTP (9200) and transport (9300) to internal networks.
Is it listening on your server?
Linux
ss -ltnp 'sport = :9200'Known vulnerabilities in Elasticsearch
| CVE | Title | CVSS | Exploited | EPSS | Published |
|---|---|---|---|---|---|
| CVE-2015-1427 | The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to by... | 9.8 | KEV | 99.9% | 2015-02-18 |
| CVE-2014-3120 | The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers... | 8.1 | KEV | 88.6% | 2014-07-29 |
| CVE-2015-5377 | Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving... | 9.8 | — | 2018-03-07 | |
| CVE-2018-3831 | Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue... | 8.8 | — | 2018-09-20 | |
| CVE-2020-7009 | Elasticsearch versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2 contain a privilege escalation flaw if a... | 8.8 | — | 2020-04-01 | |
| CVE-2020-7014 | The fix for CVE-2020-7009 was found to be incomplete. Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to... | 8.8 | — | 2020-06-04 | |
| CVE-2026-72642 | Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process | 8.8 | — | 2026-08-14 |
Track these versions on your own servers
InfraGuard collects installed software versions from every server and flags the ones with known vulnerabilities. Self-hosted — nothing leaves your network.