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(high)
- EG Risk
- —
- 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 52× in last 7d / 204× 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 384 total refreshes for this CVE.
- 2026-07-22 22:54 UTCVendor advisory
- 2026-07-22 21:54 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 18:41 UTCVendor advisory
- 2026-07-22 14:27 UTCEG score recompute
- 2026-07-22 14:27 UTCVendor advisory
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 10:14 UTCVendor advisory
- 2026-07-22 06:02 UTCVendor advisory
- 2026-07-22 01:50 UTCVendor advisory
- 2026-07-21 21:36 UTCVendor advisory
- 2026-07-21 17:22 UTCVendor advisory
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:09 UTCVendor advisory
- 2026-07-21 08:57 UTCVendor advisory
- 2026-07-21 04:45 UTCVendor advisory
- 2026-07-21 00:30 UTCVendor advisory
- 2026-07-20 20:17 UTCVendor advisory
- 2026-07-20 16:05 UTCVendor advisory
- 2026-07-20 11:54 UTCVendor advisory
- 2026-07-20 07:41 UTCVendor advisory
- 2026-07-20 03:28 UTCVendor advisory
- 2026-07-19 23:16 UTCVendor advisory
- 2026-07-19 19:04 UTCVendor advisory
- 2026-07-19 14:52 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-19 10:41 UTCVendor advisory
- 2026-07-19 06:29 UTCEG score recompute
- 2026-07-19 06:29 UTCVendor advisory
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:17 UTCVendor advisory
- 2026-07-18 22:03 UTCVendor advisory
- 2026-07-18 17:50 UTCVendor advisory
- 2026-07-18 13:37 UTCEG score recompute
- 2026-07-18 13:37 UTCVendor advisory
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-18 09:25 UTCVendor advisory
- 2026-07-18 05:13 UTCVendor advisory
- 2026-07-18 01:01 UTCVendor advisory
- 2026-07-17 20:49 UTCVendor advisory
- 2026-07-17 16:37 UTCVendor advisory
- 2026-07-17 12:24 UTCVendor advisory
- 2026-07-17 08:12 UTCEG score recompute
- 2026-07-17 08:12 UTCVendor advisory
- 2026-07-17 03:59 UTCVendor advisory
- 2026-07-16 23:47 UTCVendor advisory
- 2026-07-16 19:35 UTCVendor advisory
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 15:22 UTCVendor advisory
- 2026-07-16 11:08 UTCVendor advisory
- 2026-07-16 06:56 UTCVendor advisory
- 2026-07-16 02:44 UTCVendor advisory
- 2026-07-15 22:32 UTCVendor advisory
- 2026-07-15 18:20 UTCVendor advisory
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 14:07 UTCVendor advisory
- 2026-07-15 09:56 UTCVendor advisory
- 2026-07-15 05:42 UTCVendor advisory
- 2026-07-15 01:29 UTCVendor advisory
- 2026-07-14 21:17 UTCVendor advisory
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 17:05 UTCVendor advisory
- 2026-07-14 12:53 UTCVendor advisory
- 2026-07-14 08:41 UTCVendor advisory
- 2026-07-14 04:28 UTCVendor advisory
- 2026-07-14 00:16 UTCVendor advisory
- 2026-07-13 20:04 UTCVendor advisory
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 15:52 UTCVendor advisory
- 2026-07-13 11:39 UTCVendor advisory
- 2026-07-13 07:27 UTCVendor advisory
- 2026-07-13 06:08 UTCEPSS rescore
- 2026-07-13 03:14 UTCVendor advisory
- 2026-07-12 23:01 UTCVendor advisory
- 2026-07-12 18:48 UTCVendor advisory
- 2026-07-12 14:36 UTCVendor advisory
- 2026-07-12 10:24 UTCVendor advisory
- 2026-07-12 06:10 UTCVendor advisory
- 2026-07-12 01:56 UTCVendor advisory
- 2026-07-11 21:44 UTCVendor advisory
- 2026-07-11 17:32 UTCVendor advisory
- 2026-07-11 13:20 UTCVendor advisory
- 2026-07-11 09:08 UTCVendor advisory
- 2026-07-11 04:56 UTCVendor advisory
- 2026-07-11 00:43 UTCVendor advisory
- 2026-07-10 20:31 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 16:19 UTCVendor advisory
- 2026-07-10 12:05 UTCVendor advisory
- 2026-07-10 07:52 UTCVendor advisory
- 2026-07-10 03:38 UTCVendor advisory
- 2026-07-09 23:22 UTCVendor advisory
- 2026-07-09 19:11 UTCVendor advisory
- 2026-07-09 14:58 UTCVendor advisory
- 2026-07-09 10:46 UTCVendor advisory
- 2026-07-09 06:33 UTCVendor advisory
- 2026-07-09 02:20 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.