CVE-2014-3120

CRITICALNVD 8.19.0▲
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 89%CVSS: 8.1Exploit: cisa kev · ssvc active · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
89%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

July 28, 2014

Last Modified

April 22, 2026

Advisory Details (7)

Auto-updated May 19, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

ElasticSearch - Remote Code Execution - Multiple webapps Exploit

http://www.exploit-db.com/exploits/33370
generic

Bouke van der Bijl

http://bouk.co/blog/elasticsearch-rce/
generic

How to Secure Elasticsearch | Elastic Blog

https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearch
generic

Product Security at Elastic | Elastic

https://www.elastic.co/community/security/
generic🟡 PoC Available

Logstash 1.4.3 released | Elastic Blog

https://www.elastic.co/blog/logstash-1-4-3-released
generic
http://www.securityfocus.com/bid/67731
generic

Rapid7 Vulnerability Database

http://www.rapid7.com/db/modules/exploit/multi/elasticsearch/script_mvel_rce

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkatello-configure-0:1.4.5.1-3.el6sam2014-09-11redhat
redhatpatch2014-09-10redhat
redhatpatch2014-09-10redhat

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)
PackageVulnerable rangeFixed inDependents
org.elasticsearch:elasticsearch0.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 49× in last 7d / 203× 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 599 total refreshes for this CVE.

  1. 2026-08-26 03:28 UTCVendor advisory
  2. 2026-08-25 23:16 UTCVendor advisory
  3. 2026-08-25 19:05 UTCVendor advisory
  4. 2026-08-25 14:51 UTCVendor advisory
  5. 2026-08-25 10:39 UTCVendor advisory
  6. 2026-08-25 06:26 UTCVendor advisory
  7. 2026-08-25 02:13 UTCVendor advisory
  8. 2026-08-24 22:01 UTCVendor advisory
  9. 2026-08-24 18:52 UTCCISA KEV update
  10. 2026-08-24 17:49 UTCEG score recompute
  11. 2026-08-24 17:49 UTCVendor advisory
  12. 2026-08-24 13:38 UTCVendor advisory
  13. 2026-08-24 09:26 UTCEG score recompute
  14. 2026-08-24 09:26 UTCVendor advisory
  15. 2026-08-24 05:13 UTCVendor advisory
  16. 2026-08-24 01:01 UTCVendor advisory
  17. 2026-08-23 20:49 UTCVendor advisory
  18. 2026-08-23 16:37 UTCVendor advisory
  19. 2026-08-23 12:25 UTCVendor advisory
  20. 2026-08-23 08:13 UTCVendor advisory
  21. 2026-08-23 04:01 UTCEG score recompute
  22. 2026-08-23 04:01 UTCVendor advisory
  23. 2026-08-22 23:49 UTCVendor advisory
  24. 2026-08-22 19:37 UTCVendor advisory
  25. 2026-08-22 15:25 UTCVendor advisory
Show 75 more
  1. 2026-08-22 11:13 UTCVendor advisory
  2. 2026-08-22 07:01 UTCVendor advisory
  3. 2026-08-22 02:48 UTCVendor advisory
  4. 2026-08-21 22:36 UTCVendor advisory
  5. 2026-08-21 18:24 UTCVendor advisory
  6. 2026-08-21 16:49 UTCCISA KEV update
  7. 2026-08-21 14:12 UTCVendor advisory
  8. 2026-08-21 10:00 UTCVendor advisory
  9. 2026-08-21 05:48 UTCVendor advisory
  10. 2026-08-21 01:36 UTCVendor advisory
  11. 2026-08-20 21:23 UTCVendor advisory
  12. 2026-08-20 17:11 UTCVendor advisory
  13. 2026-08-20 17:06 UTCCISA KEV update
  14. 2026-08-20 12:58 UTCVendor advisory
  15. 2026-08-20 08:45 UTCVendor advisory
  16. 2026-08-20 04:33 UTCVendor advisory
  17. 2026-08-20 00:21 UTCVendor advisory
  18. 2026-08-19 20:08 UTCEG score recompute
  19. 2026-08-19 20:08 UTCVendor advisory
  20. 2026-08-19 17:33 UTCCISA KEV update
  21. 2026-08-19 16:59 UTCEPSS rescore
  22. 2026-08-19 15:53 UTCVendor advisory
  23. 2026-08-19 11:41 UTCVendor advisory
  24. 2026-08-19 07:29 UTCVendor advisory
  25. 2026-08-19 03:16 UTCVendor advisory
  26. 2026-08-18 23:02 UTCVendor advisory
  27. 2026-08-18 18:51 UTCVendor advisory
  28. 2026-08-18 16:58 UTCCISA KEV update
  29. 2026-08-18 14:38 UTCVendor advisory
  30. 2026-08-18 10:13 UTCVendor advisory
  31. 2026-08-18 06:00 UTCVendor advisory
  32. 2026-08-18 01:48 UTCVendor advisory
  33. 2026-08-17 21:35 UTCVendor advisory
  34. 2026-08-17 17:21 UTCEG score recompute
  35. 2026-08-17 17:21 UTCVendor advisory
  36. 2026-08-17 13:56 UTCCISA KEV update
  37. 2026-08-17 13:09 UTCVendor advisory
  38. 2026-08-17 08:57 UTCVendor advisory
  39. 2026-08-17 04:46 UTCVendor advisory
  40. 2026-08-17 00:34 UTCVendor advisory
  41. 2026-08-16 20:22 UTCVendor advisory
  42. 2026-08-16 16:10 UTCVendor advisory
  43. 2026-08-16 11:58 UTCVendor advisory
  44. 2026-08-16 07:46 UTCVendor advisory
  45. 2026-08-16 03:35 UTCEG score recompute
  46. 2026-08-16 03:35 UTCVendor advisory
  47. 2026-08-16 02:09 UTCEPSS rescore
  48. 2026-08-15 23:23 UTCVendor advisory
  49. 2026-08-15 19:11 UTCVendor advisory
  50. 2026-08-15 14:59 UTCVendor advisory
  51. 2026-08-15 10:47 UTCVendor advisory
  52. 2026-08-15 06:35 UTCVendor advisory
  53. 2026-08-15 02:22 UTCVendor advisory
  54. 2026-08-14 22:11 UTCVendor advisory
  55. 2026-08-14 17:59 UTCVendor advisory
  56. 2026-08-14 13:47 UTCVendor advisory
  57. 2026-08-14 09:35 UTCVendor advisory
  58. 2026-08-14 05:23 UTCVendor advisory
  59. 2026-08-14 01:11 UTCVendor advisory
  60. 2026-08-13 20:59 UTCVendor advisory
  61. 2026-08-13 16:47 UTCVendor advisory
  62. 2026-08-13 12:35 UTCVendor advisory
  63. 2026-08-13 08:23 UTCVendor advisory
  64. 2026-08-13 04:11 UTCVendor advisory
  65. 2026-08-12 23:59 UTCVendor advisory
  66. 2026-08-12 19:47 UTCVendor advisory
  67. 2026-08-12 15:35 UTCEG score recompute
  68. 2026-08-12 15:35 UTCVendor advisory
  69. 2026-08-12 13:46 UTCEPSS rescore
  70. 2026-08-12 11:24 UTCVendor advisory
  71. 2026-08-12 07:11 UTCVendor advisory
  72. 2026-08-12 02:59 UTCVendor advisory
  73. 2026-08-11 22:47 UTCVendor advisory
  74. 2026-08-11 19:32 UTCCISA KEV update
  75. 2026-08-11 18:35 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-3120
    First seen Jul 7, 2014

    POC Code to exploite CVE-2014-3120

    Open source ↗
  • Exploit-DBEDB-33588✓ verified
    First seen May 30, 2014

    ElasticSearch Dynamic Script - Arbitrary Java Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-33370✓ verified
    First seen May 15, 2014

    ElasticSearch - Remote Code Execution

    Open source ↗
  • Nucleihttp/cves/2014/CVE-2014-3120.yaml
    First seen Jan 1, 2014

    ElasticSearch v1.1.1/1.2 RCE

    Open source ↗
  • Metasploitexploit/multi/elasticsearch/script_mvel_rce✓ verified
    First seen Dec 9, 2013

    ElasticSearch Dynamic Script Arbitrary Java Execution

    Open source ↗

Related CVEs(same vendor)

Frequently asked(6)

What is CVE-2014-3120?
CVE-2014-3120 is a critical vulnerability published on July 28, 2014. 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…
When was CVE-2014-3120 disclosed?
CVE-2014-3120 was first published in the National Vulnerability Database on July 28, 2014, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-3120 actively exploited?
Yes. CISA added CVE-2014-3120 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Elastic Elasticsearch. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2014-3120?
CVE-2014-3120 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2014-3120?
CVE-2014-3120 affects Elastic Elasticsearch. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2014-3120?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-3120, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-3120

Explore →

Is Your Infrastructure Affected by CVE-2014-3120?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs