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 PROB
- 100%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
February 17, 2015
Last Modified
April 22, 2026
Advisory Details (7)
Auto-updated Sep 17, 2026Packet Storm Security
http://packetstormsecurity.com/files/130784/ElasticSearch-Unauthenticated-Remote-Code-Execution.htmlLocked Out | Packet Storm
http://packetstormsecurity.com/files/130368/Elasticsearch-1.3.7-1.4.2-Sandbox-Escape-Command-Execution.htmlVendor Advisories for CVE-2015-1427(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch 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 | — |
Data Freshness Timeline
(refreshed 50× in last 7d / 214× 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 793 total refreshes for this CVE.
- 2026-09-19 05:31 UTCVendor advisory
- 2026-09-19 01:46 UTCVendor advisory
- 2026-09-18 22:03 UTCVendor advisory
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 18:19 UTCVendor advisory
- 2026-09-18 14:36 UTCVendor advisory
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 10:52 UTCVendor advisory
- 2026-09-18 07:08 UTCVendor advisory
- 2026-09-18 03:25 UTCVendor advisory
- 2026-09-17 23:41 UTCVendor advisory
- 2026-09-17 19:58 UTCVendor advisory
- 2026-09-17 16:14 UTCVendor advisory
- 2026-09-17 12:31 UTCVendor advisory
- 2026-09-17 08:43 UTCVendor advisory
- 2026-09-17 04:59 UTCVendor advisory
- 2026-09-17 01:15 UTCVendor advisory
- 2026-09-16 21:32 UTCVendor advisory
- 2026-09-16 17:48 UTCVendor advisory
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:05 UTCEG score recompute
- 2026-09-16 14:05 UTCVendor advisory
- 2026-09-16 10:21 UTCVendor advisory
- 2026-09-16 06:37 UTCVendor advisory
- 2026-09-16 02:54 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-15 23:10 UTCVendor advisory
- 2026-09-15 19:26 UTCVendor advisory
- 2026-09-15 15:42 UTCVendor advisory
- 2026-09-15 11:58 UTCVendor advisory
- 2026-09-15 08:15 UTCVendor advisory
- 2026-09-15 04:31 UTCVendor advisory
- 2026-09-15 00:47 UTCVendor advisory
- 2026-09-14 21:03 UTCVendor advisory
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 17:19 UTCVendor advisory
- 2026-09-14 13:35 UTCVendor advisory
- 2026-09-14 09:52 UTCVendor advisory
- 2026-09-14 06:05 UTCVendor advisory
- 2026-09-14 02:21 UTCVendor advisory
- 2026-09-13 22:38 UTCVendor advisory
- 2026-09-13 18:54 UTCVendor advisory
- 2026-09-13 15:10 UTCVendor advisory
- 2026-09-13 11:26 UTCVendor advisory
- 2026-09-13 07:42 UTCVendor advisory
- 2026-09-13 03:59 UTCVendor advisory
- 2026-09-13 00:15 UTCVendor advisory
- 2026-09-12 20:31 UTCVendor advisory
- 2026-09-12 16:47 UTCVendor advisory
- 2026-09-12 13:03 UTCVendor advisory
- 2026-09-12 09:20 UTCVendor advisory
- 2026-09-12 05:36 UTCVendor advisory
- 2026-09-12 01:53 UTCVendor advisory
- 2026-09-11 22:09 UTCVendor advisory
- 2026-09-11 18:49 UTCCISA KEV update
- 2026-09-11 18:26 UTCVendor advisory
- 2026-09-11 14:42 UTCVendor advisory
- 2026-09-11 10:58 UTCVendor advisory
- 2026-09-11 07:14 UTCVendor advisory
- 2026-09-11 03:30 UTCVendor advisory
- 2026-09-10 23:46 UTCVendor advisory
- 2026-09-10 20:02 UTCVendor advisory
- 2026-09-10 19:28 UTCCISA KEV update
- 2026-09-10 16:19 UTCVendor advisory
- 2026-09-10 12:35 UTCVendor advisory
- 2026-09-10 08:51 UTCVendor advisory
- 2026-09-10 05:07 UTCVendor advisory
- 2026-09-10 01:24 UTCVendor advisory
- 2026-09-09 21:37 UTCVendor advisory
- 2026-09-09 19:08 UTCCISA KEV update
- 2026-09-09 17:53 UTCVendor advisory
- 2026-09-09 14:09 UTCVendor advisory
- 2026-09-09 10:25 UTCVendor advisory
- 2026-09-09 06:42 UTCVendor advisory
- 2026-09-09 02:58 UTCVendor advisory
- 2026-09-08 23:14 UTCVendor advisory
- 2026-09-08 19:31 UTCVendor advisory
- 2026-09-08 18:54 UTCCISA KEV update
- 2026-09-08 15:46 UTCVendor advisory
- 2026-09-08 11:57 UTCVendor advisory
- 2026-09-08 08:11 UTCVendor advisory
- 2026-09-08 04:25 UTCVendor advisory
- 2026-09-08 00:41 UTCVendor advisory
- 2026-09-07 20:57 UTCVendor advisory
- 2026-09-07 17:14 UTCVendor advisory
- 2026-09-07 13:31 UTCVendor advisory
- 2026-09-07 09:45 UTCVendor advisory
- 2026-09-07 05:59 UTCVendor advisory
- 2026-09-07 02:16 UTCVendor advisory
- 2026-09-06 22:30 UTCVendor advisory
- 2026-09-06 18:46 UTCVendor advisory
- 2026-09-06 15:02 UTCVendor advisory
- 2026-09-06 11:18 UTCVendor advisory
- 2026-09-06 07:35 UTCVendor advisory
- 2026-09-06 03:51 UTCVendor advisory
- 2026-09-06 00:08 UTCVendor advisory
- 2026-09-05 20:24 UTCVendor advisory
- 2026-09-05 16:41 UTCVendor advisory
- 2026-09-05 12:57 UTCVendor advisory
- 2026-09-05 09:12 UTCVendor advisory
- 2026-09-05 05:28 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 ↗
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.