Exploited CVEs / CVE-2014-3120
CVE-2014-3120
Elasticsearch Remote Code Execution Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-04-15 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Risk summary
Actively exploited Elastic Elasticsearch vulnerability, High severity, CVSS v3 8.1. Added to the CISA KEV catalog 2022-03-25.
Senserva AI Opinion for CVE-2014-3120
Early Elasticsearch shipped with dynamic scripting enabled, allowing anyone who could reach the REST API to run MVEL expressions and arbitrary Java code on the node. The 89% EPSS score reflects constant automated exploitation of internet-exposed clusters, often for cryptomining. Any old Elasticsearch instance reachable beyond localhost should be treated as compromised until proven otherwise.
Do this: Find Elasticsearch nodes exposed to untrusted networks and upgrade them or firewall the REST API now.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2014-3120
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Updated August 21, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Full tracking and change history for CVE-2014-3120
- Published
- 2022-03-25
- Last revised
- 2022-03-25
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
- 2022-03-25 added to the CISA KEV catalog by CISA
- 2026-07-17 CVSS 0.0 to 8.1; EPSS first scored at 88.6%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
CISA required action
Federal (BOD 22-01) remediation due date: 2022-04-15 (past due).
Apply updates per vendor instructions.
Official fix for CVE-2014-3120
Check the vendor's security advisory channel for the patched Elasticsearch versions and workarounds.
Common questions about CVE-2014-3120
Is CVE-2014-3120 actively exploited?
Yes. CVE-2014-3120 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 89%.
What is the CISA deadline and required action for CVE-2014-3120?
CISA set the federal (BOD 22-01) remediation due date at 2022-04-15, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply updates per vendor instructions.
What fixes CVE-2014-3120?
Check the vendor's security advisory for the patched Elasticsearch versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2014-3120?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2014-3120's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
Scope and sources
- More exploited Elastic CVEs
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.