CVE-2014-3120

HIGHNVD 8.19.0
EchelonGraph scoreMEDIUM 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 — 3 sources updated this weekExploited in the wild
8.1
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 89%CVSS: 8.1Exploit: NoneExposed: 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(medium)
EPSS
99.8%
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

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

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 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.

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

Frequently asked(6)

What is CVE-2014-3120?
CVE-2014-3120 is a high 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.