# Elasticsearch vulnerabilities > Elasticsearch is made by Elastic. We track 42 published vulnerabilities listed under that exact name, across 371 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 March 2022. Elastic lists newer releases under their own names, such as Elasticsearch X-Pack, so check those pages too. Canonical page: https://www.precursorintelligence.com/product/elastic/elasticsearch ## At a glance - **Made by:** [Elastic](https://www.precursorintelligence.com/vendors/elastic) - **Published vulnerabilities:** 42 - **Known to be exploited:** 1 (listed under the name Elasticsearch) - **Versions tracked:** 371 - **Most recently added to the known-exploited list:** [CVE-2015-1427](https://www.precursorintelligence.com/what-is/cve-2015-1427), 25 March 2022. We keep watching the list. ## Is Elasticsearch listed under other names? Elastic also lists Elasticsearch under more specific names, such as Elasticsearch X-Pack. Flaws listed only under those names are counted on their own pages, not here. - [Elasticsearch X-Pack](https://www.precursorintelligence.com/product/elastic/elasticsearch_x-pack): 2 published vulnerabilities ## Which versions of Elasticsearch do the exploited flaws hit? Each exploited flaw lists the versions it affects, as published. "before 1.3.8" means every version up to, but not including, 1.3.8. - [CVE-2015-1427](https://www.precursorintelligence.com/what-is/cve-2015-1427) (Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability): before 1.3.8, 1.4.0 to before 1.4.3 ## Which Elasticsearch vulnerabilities are being exploited? 1 flaw is on the government list of vulnerabilities known to be exploited, newest first: - [CVE-2015-1427](https://www.precursorintelligence.com/what-is/cve-2015-1427): Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability. Critical, CVSS 9.8, chance of use in 30 days >99%, known exploited since 25 March 2022. ## Which Elasticsearch flaws are most likely to be used? Ranked by the latest exploit-likelihood forecast (the chance each flaw is used in an attack in the next 30 days): - [CVE-2015-1427](https://www.precursorintelligence.com/what-is/cve-2015-1427): >99%, Critical (CVSS 9.8), known exploited - [CVE-2021-22145](https://www.precursorintelligence.com/what-is/cve-2021-22145): 76%, Medium (CVSS 6.5) - [CVE-2023-31419](https://www.precursorintelligence.com/what-is/cve-2023-31419): 62%, Medium (CVSS 6.5) - [CVE-2021-22146](https://www.precursorintelligence.com/what-is/cve-2021-22146): 36%, High (CVSS 7.5) - [CVE-2015-5377](https://www.precursorintelligence.com/what-is/cve-2015-5377): 14%, Critical (CVSS 9.8) - [CVE-2022-23712](https://www.precursorintelligence.com/what-is/cve-2022-23712): 7.5%, High (CVSS 7.5) - [CVE-2021-22144](https://www.precursorintelligence.com/what-is/cve-2021-22144): 2.4%, Medium (CVSS 6.5) - [CVE-2019-7619](https://www.precursorintelligence.com/what-is/cve-2019-7619): 2.4%, Medium (CVSS 5.3) - [CVE-2019-7611](https://www.precursorintelligence.com/what-is/cve-2019-7611): 2.1%, High (CVSS 8.1) - [CVE-2023-31418](https://www.precursorintelligence.com/what-is/cve-2023-31418): 2.1%, High (CVSS 7.5) ## Questions ### How many vulnerabilities does Elasticsearch have? We track 42 published vulnerabilities listed under the name Elasticsearch, across 371 versions. The most recent Elasticsearch flaw added to the known-exploited list is CVE-2015-1427, on 25 March 2022. ### Which Elasticsearch vulnerabilities are being exploited? 1 is on the list of flaws known to be exploited. The most recently added is CVE-2015-1427. ### Why are newer Elasticsearch flaws missing from this page? Elastic also lists Elasticsearch under more specific names, such as Elasticsearch X-Pack. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list. ### Which versions of Elasticsearch do the exploited flaws affect? Each flaw names its own versions, usually as ranges. The newest, CVE-2015-1427, affects before 1.3.8, 1.4.0 to before 1.4.3. The versions for every exploited flaw are listed on this page. ### How do I get alerts for Elasticsearch? Create a Precursor Intelligence account and track Elasticsearch. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook. ## Running Elasticsearch? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact