The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine.
CVE-2014-3120
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.1 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 9.0(medium)
- EPSS
- 99.8%
- KEV
- ⚠ Exploited
Published
July 28, 2014
Last Modified
April 22, 2026
Advisory Details (7)
Auto-updated May 19, 2026ElasticSearch - Remote Code Execution - Multiple webapps Exploit
http://www.exploit-db.com/exploits/33370How to Secure Elasticsearch | Elastic Blog
https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearchLogstash 1.4.3 released | Elastic Blog
https://www.elastic.co/blog/logstash-1-4-3-releasedRapid7 Vulnerability Database
http://www.rapid7.com/db/modules/exploit/multi/elasticsearch/script_mvel_rcePatch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | katello-configure-0:1.4.5.1-3.el6sam | 2014-09-11 | redhat |
| redhat | patch | 2014-09-10 | redhat |
| redhat | patch | 2014-09-10 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.elasticsearch:elasticsearch | 0.10.0 ... 1.3.9 (111 versions) | 1.4.0.Beta1 | — |
All Vendor Advisories
(3)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 83× in last 7d / 360× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 545 total refreshes for this CVE.
- 2026-07-12 01:56 UTCEG score recompute
- 2026-07-12 01:56 UTCVendor advisory
- 2026-07-11 21:44 UTCEG score recompute
- 2026-07-11 21:44 UTCVendor advisory
- 2026-07-11 17:32 UTCEG score recompute
- 2026-07-11 17:32 UTCVendor advisory
- 2026-07-11 13:20 UTCEG score recompute
- 2026-07-11 13:20 UTCVendor advisory
- 2026-07-11 09:08 UTCEG score recompute
- 2026-07-11 09:08 UTCVendor advisory
- 2026-07-11 04:56 UTCEG score recompute
- 2026-07-11 04:56 UTCVendor advisory
- 2026-07-11 00:43 UTCEG score recompute
- 2026-07-11 00:43 UTCVendor advisory
- 2026-07-10 20:31 UTCEG score recompute
- 2026-07-10 20:31 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 16:19 UTCEG score recompute
- 2026-07-10 16:19 UTCVendor advisory
- 2026-07-10 12:05 UTCEG score recompute
- 2026-07-10 12:05 UTCVendor advisory
- 2026-07-10 07:52 UTCEG score recompute
- 2026-07-10 07:52 UTCVendor advisory
- 2026-07-10 03:38 UTCEG score recompute
- 2026-07-10 03:38 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-09 23:22 UTCEG score recompute
- 2026-07-09 23:22 UTCVendor advisory
- 2026-07-09 19:11 UTCEG score recompute
- 2026-07-09 19:11 UTCVendor advisory
- 2026-07-09 14:58 UTCEG score recompute
- 2026-07-09 14:58 UTCVendor advisory
- 2026-07-09 10:46 UTCEG score recompute
- 2026-07-09 10:46 UTCVendor advisory
- 2026-07-09 06:33 UTCEG score recompute
- 2026-07-09 06:33 UTCVendor advisory
- 2026-07-09 02:20 UTCEG score recompute
- 2026-07-09 02:20 UTCVendor advisory
- 2026-07-08 22:07 UTCEG score recompute
- 2026-07-08 22:07 UTCVendor advisory
- 2026-07-08 17:53 UTCEG score recompute
- 2026-07-08 17:53 UTCVendor advisory
- 2026-07-08 13:40 UTCEG score recompute
- 2026-07-08 13:40 UTCVendor advisory
- 2026-07-08 09:24 UTCEG score recompute
- 2026-07-08 09:24 UTCVendor advisory
- 2026-07-08 05:12 UTCEG score recompute
- 2026-07-08 05:12 UTCVendor advisory
- 2026-07-08 00:59 UTCEG score recompute
- 2026-07-08 00:59 UTCVendor advisory
- 2026-07-07 20:47 UTCEG score recompute
- 2026-07-07 20:47 UTCVendor advisory
- 2026-07-07 19:01 UTCCISA KEV update
- 2026-07-07 17:16 UTCCISA KEV update
- 2026-07-07 16:34 UTCEG score recompute
- 2026-07-07 16:34 UTCVendor advisory
- 2026-07-07 12:20 UTCEG score recompute
- 2026-07-07 12:20 UTCVendor advisory
- 2026-07-07 08:06 UTCEG score recompute
- 2026-07-07 08:06 UTCVendor advisory
- 2026-07-07 03:52 UTCEG score recompute
- 2026-07-07 03:52 UTCVendor advisory
- 2026-07-06 23:37 UTCEG score recompute
- 2026-07-06 23:37 UTCVendor advisory
- 2026-07-06 19:24 UTCEG score recompute
- 2026-07-06 19:24 UTCVendor advisory
- 2026-07-06 15:07 UTCEG score recompute
- 2026-07-06 15:07 UTCVendor advisory
- 2026-07-06 10:53 UTCEG score recompute
- 2026-07-06 10:53 UTCVendor advisory
- 2026-07-06 06:41 UTCEG score recompute
- 2026-07-06 06:41 UTCVendor advisory
- 2026-07-06 02:29 UTCEG score recompute
- 2026-07-06 02:29 UTCVendor advisory
- 2026-07-05 22:17 UTCEG score recompute
- 2026-07-05 22:17 UTCVendor advisory
- 2026-07-05 18:05 UTCEG score recompute
- 2026-07-05 18:05 UTCVendor advisory
- 2026-07-05 13:52 UTCEG score recompute
- 2026-07-05 13:52 UTCVendor advisory
- 2026-07-05 09:40 UTCEG score recompute
- 2026-07-05 09:40 UTCVendor advisory
- 2026-07-05 05:28 UTCEG score recompute
- 2026-07-05 05:28 UTCVendor advisory
- 2026-07-05 01:13 UTCEG score recompute
- 2026-07-05 01:13 UTCVendor advisory
- 2026-07-04 21:00 UTCEG score recompute
- 2026-07-04 21:00 UTCVendor advisory
- 2026-07-04 16:48 UTCEG score recompute
- 2026-07-04 16:48 UTCVendor advisory
- 2026-07-04 12:32 UTCEG score recompute
- 2026-07-04 12:32 UTCVendor advisory
- 2026-07-04 08:20 UTCEG score recompute
- 2026-07-04 08:20 UTCVendor advisory
- 2026-07-04 06:27 UTCEPSS rescore
- 2026-07-04 04:08 UTCEG score recompute
- 2026-07-04 04:08 UTCVendor advisory
- 2026-07-03 23:56 UTCEG score recompute
- 2026-07-03 23:56 UTCVendor advisory
- 2026-07-03 19:43 UTCEG score recompute
- 2026-07-03 19:43 UTCVendor advisory
Publicly available exploits
(5 references)Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCechohtp/ElasticSearch-CVE-2014-3120First seen Jul 7, 2014
POC Code to exploite CVE-2014-3120
Open source ↗ - Exploit-DBEDB-33588✓ verifiedFirst seen May 30, 2014
ElasticSearch Dynamic Script - Arbitrary Java Execution (Metasploit)
Open source ↗ - Exploit-DBEDB-33370✓ verifiedFirst seen May 15, 2014
ElasticSearch - Remote Code Execution
Open source ↗ - Nucleihttp/cves/2014/CVE-2014-3120.yamlFirst seen Jan 1, 2014
ElasticSearch v1.1.1/1.2 RCE
Open source ↗ - Metasploitexploit/multi/elasticsearch/script_mvel_rce✓ verifiedFirst seen Dec 9, 2013
ElasticSearch Dynamic Script Arbitrary Java Execution
Open source ↗
Frequently asked(6)
What is CVE-2014-3120?
When was CVE-2014-3120 disclosed?
Is CVE-2014-3120 actively exploited?
What is the CVSS score of CVE-2014-3120?
Which products are affected by CVE-2014-3120?
How do I remediate CVE-2014-3120?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-3120
Is Your Infrastructure Affected by CVE-2014-3120?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.