The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script.
CVE-2015-1427
Score elevated to 9.8 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 9.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 99(Act)EG Risk 99/100SSVC: Act
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 computedSeverity98% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Fix now — active exploitation, automatable, high impact. - EPSS
- 100.0%
- KEV
- ⚠ Exploited
Published
February 17, 2015
Last Modified
April 22, 2026
Advisory Details (6)
Auto-updated May 12, 2026Packet Storm
http://packetstormsecurity.com/files/130784/ElasticSearch-Unauthenticated-Remote-Code-Execution.htmlPatch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | patch | 2017-04-03 | 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 | 1.4.0, 1.4.1, 1.4.2 | 1.4.3 | — |
All Vendor Advisories
(1)
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 50× in last 7d / 211× 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 401 total refreshes for this CVE.
- 2026-07-23 01:16 UTCEG score recompute
- 2026-07-23 00:15 UTCEG score recompute
- 2026-07-23 00:15 UTCVendor advisory
- 2026-07-22 21:57 UTCEG score recompute
- 2026-07-22 20:30 UTCVendor advisory
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:46 UTCVendor advisory
- 2026-07-22 12:55 UTCVendor advisory
- 2026-07-22 09:11 UTCVendor advisory
- 2026-07-22 05:24 UTCVendor advisory
- 2026-07-22 01:16 UTCVendor advisory
- 2026-07-21 20:24 UTCVendor advisory
- 2026-07-21 16:39 UTCVendor advisory
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:55 UTCVendor advisory
- 2026-07-21 09:06 UTCVendor advisory
- 2026-07-21 05:20 UTCVendor advisory
- 2026-07-21 01:35 UTCVendor advisory
- 2026-07-20 21:51 UTCVendor advisory
- 2026-07-20 18:07 UTCVendor advisory
- 2026-07-20 14:21 UTCVendor advisory
- 2026-07-20 10:38 UTCVendor advisory
- 2026-07-20 06:53 UTCVendor advisory
- 2026-07-20 02:59 UTCVendor advisory
- 2026-07-19 23:15 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-19 19:31 UTCVendor advisory
- 2026-07-19 15:47 UTCVendor advisory
- 2026-07-19 12:04 UTCVendor advisory
- 2026-07-19 08:20 UTCVendor advisory
- 2026-07-19 04:36 UTCVendor advisory
- 2026-07-19 00:52 UTCVendor advisory
- 2026-07-18 21:09 UTCVendor advisory
- 2026-07-18 17:25 UTCVendor advisory
- 2026-07-18 13:42 UTCVendor advisory
- 2026-07-18 09:57 UTCVendor advisory
- 2026-07-18 06:13 UTCVendor advisory
- 2026-07-18 02:28 UTCVendor advisory
- 2026-07-17 22:43 UTCVendor advisory
- 2026-07-17 18:59 UTCVendor advisory
- 2026-07-17 15:15 UTCVendor advisory
- 2026-07-17 07:46 UTCEG score recompute
- 2026-07-17 07:46 UTCVendor advisory
- 2026-07-17 04:02 UTCVendor advisory
- 2026-07-17 00:18 UTCVendor advisory
- 2026-07-16 20:35 UTCVendor advisory
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:51 UTCVendor advisory
- 2026-07-16 12:55 UTCVendor advisory
- 2026-07-16 09:11 UTCVendor advisory
- 2026-07-16 05:27 UTCVendor advisory
- 2026-07-16 01:43 UTCVendor advisory
- 2026-07-15 21:59 UTCVendor advisory
- 2026-07-15 18:15 UTCVendor advisory
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 14:31 UTCVendor advisory
- 2026-07-15 10:47 UTCVendor advisory
- 2026-07-15 07:02 UTCVendor advisory
- 2026-07-15 03:18 UTCVendor advisory
- 2026-07-14 23:34 UTCVendor advisory
- 2026-07-14 19:50 UTCVendor advisory
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 16:07 UTCVendor advisory
- 2026-07-14 12:23 UTCVendor advisory
- 2026-07-14 08:39 UTCVendor advisory
- 2026-07-14 04:53 UTCVendor advisory
- 2026-07-14 01:09 UTCVendor advisory
- 2026-07-13 21:25 UTCVendor advisory
- 2026-07-13 17:41 UTCVendor advisory
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 13:57 UTCVendor advisory
- 2026-07-13 10:14 UTCVendor advisory
- 2026-07-13 06:30 UTCVendor advisory
- 2026-07-13 02:43 UTCVendor advisory
- 2026-07-12 22:59 UTCVendor advisory
- 2026-07-12 19:15 UTCVendor advisory
- 2026-07-12 15:31 UTCVendor advisory
- 2026-07-12 11:46 UTCVendor advisory
- 2026-07-12 08:02 UTCVendor advisory
- 2026-07-12 04:18 UTCVendor advisory
- 2026-07-12 00:34 UTCVendor advisory
- 2026-07-11 20:50 UTCVendor advisory
- 2026-07-11 17:06 UTCVendor advisory
- 2026-07-11 13:22 UTCVendor advisory
- 2026-07-11 09:38 UTCVendor advisory
- 2026-07-11 05:54 UTCVendor advisory
- 2026-07-11 02:10 UTCVendor advisory
- 2026-07-10 22:25 UTCVendor advisory
- 2026-07-10 18:39 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 14:55 UTCVendor advisory
- 2026-07-10 11:11 UTCVendor advisory
- 2026-07-10 07:28 UTCVendor advisory
- 2026-07-10 03:43 UTCVendor advisory
- 2026-07-09 23:59 UTCVendor advisory
- 2026-07-09 20:16 UTCVendor advisory
- 2026-07-09 19:05 UTCEPSS rescore
- 2026-07-09 16:31 UTCVendor advisory
- 2026-07-09 12:48 UTCVendor advisory
- 2026-07-09 09:04 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 PoCt0kx/exploit-CVE-2015-1427First seen Jan 9, 2017
Elasticsearch 1.4.0 < 1.4.2 Remote Code Execution exploit and vulnerable container
Open source ↗ - Exploit-DBEDB-36415✓ verifiedFirst seen Mar 16, 2015
ElasticSearch - Search Groovy Sandbox Bypass (Metasploit)
Open source ↗ - Exploit-DBEDB-36337✓ verifiedFirst seen Mar 11, 2015
ElasticSearch - Remote Code Execution
Open source ↗ - Metasploitexploit/multi/elasticsearch/search_groovy_script✓ verifiedFirst seen Feb 11, 2015
ElasticSearch Search Groovy Sandbox Bypass
Open source ↗ - Nucleihttp/cves/2015/CVE-2015-1427.yamlFirst seen Jan 1, 2015
ElasticSearch - Remote Code Execution
Open source ↗
Related CVEs(same vendor)
Frequently asked(6)
What is CVE-2015-1427?
When was CVE-2015-1427 disclosed?
Is CVE-2015-1427 actively exploited?
What is the CVSS score of CVE-2015-1427?
Which products are affected by CVE-2015-1427?
How do I remediate CVE-2015-1427?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-1427
Is Your Infrastructure Affected by CVE-2015-1427?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.