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 Aug 19, 2026Packet Storm Security
http://packetstormsecurity.com/files/130784/ElasticSearch-Unauthenticated-Remote-Code-Execution.htmlPSIRT.COM — Product Security Incident Response Team
http://www.securityfocus.com/archive/1/534689/100/0/threadedLocked 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 52× in last 7d / 212× 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 623 total refreshes for this CVE.
- 2026-08-26 01:42 UTCVendor advisory
- 2026-08-25 21:59 UTCVendor advisory
- 2026-08-25 18:15 UTCVendor advisory
- 2026-08-25 14:31 UTCEG score recompute
- 2026-08-25 14:31 UTCVendor advisory
- 2026-08-25 13:44 UTCEPSS rescore
- 2026-08-25 10:48 UTCVendor advisory
- 2026-08-25 07:05 UTCVendor advisory
- 2026-08-25 03:21 UTCVendor advisory
- 2026-08-24 23:38 UTCVendor advisory
- 2026-08-24 19:54 UTCVendor advisory
- 2026-08-24 18:52 UTCCISA KEV update
- 2026-08-24 16:11 UTCEG score recompute
- 2026-08-24 16:11 UTCVendor advisory
- 2026-08-24 12:27 UTCVendor advisory
- 2026-08-24 08:43 UTCVendor advisory
- 2026-08-24 05:00 UTCVendor advisory
- 2026-08-24 01:16 UTCVendor advisory
- 2026-08-23 21:32 UTCVendor advisory
- 2026-08-23 17:49 UTCVendor advisory
- 2026-08-23 14:06 UTCVendor advisory
- 2026-08-23 10:22 UTCVendor advisory
- 2026-08-23 06:38 UTCVendor advisory
- 2026-08-23 02:55 UTCVendor advisory
- 2026-08-22 23:11 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-22 19:27 UTCVendor advisory
- 2026-08-22 15:43 UTCVendor advisory
- 2026-08-22 11:55 UTCVendor advisory
- 2026-08-22 08:11 UTCVendor advisory
- 2026-08-22 04:27 UTCVendor advisory
- 2026-08-22 00:44 UTCVendor advisory
- 2026-08-21 21:00 UTCVendor advisory
- 2026-08-21 17:17 UTCVendor advisory
- 2026-08-21 16:49 UTCCISA KEV update
- 2026-08-21 13:33 UTCVendor advisory
- 2026-08-21 09:49 UTCVendor advisory
- 2026-08-21 06:06 UTCVendor advisory
- 2026-08-21 02:23 UTCVendor advisory
- 2026-08-20 22:39 UTCVendor advisory
- 2026-08-20 18:56 UTCVendor advisory
- 2026-08-20 17:06 UTCCISA KEV update
- 2026-08-20 15:12 UTCVendor advisory
- 2026-08-20 11:29 UTCVendor advisory
- 2026-08-20 07:45 UTCVendor advisory
- 2026-08-20 04:02 UTCVendor advisory
- 2026-08-20 00:18 UTCVendor advisory
- 2026-08-19 20:34 UTCVendor advisory
- 2026-08-19 17:33 UTCCISA KEV update
- 2026-08-19 16:50 UTCVendor advisory
- 2026-08-19 13:06 UTCVendor advisory
- 2026-08-19 09:23 UTCVendor advisory
- 2026-08-19 05:39 UTCVendor advisory
- 2026-08-19 01:55 UTCVendor advisory
- 2026-08-18 22:12 UTCVendor advisory
- 2026-08-18 18:27 UTCVendor advisory
- 2026-08-18 16:58 UTCCISA KEV update
- 2026-08-18 14:43 UTCVendor advisory
- 2026-08-18 10:57 UTCVendor advisory
- 2026-08-18 07:13 UTCVendor advisory
- 2026-08-18 03:29 UTCVendor advisory
- 2026-08-17 23:43 UTCVendor advisory
- 2026-08-17 20:00 UTCVendor advisory
- 2026-08-17 16:14 UTCVendor advisory
- 2026-08-17 13:56 UTCCISA KEV update
- 2026-08-17 12:30 UTCVendor advisory
- 2026-08-17 08:47 UTCVendor advisory
- 2026-08-17 05:04 UTCVendor advisory
- 2026-08-17 01:20 UTCVendor advisory
- 2026-08-16 21:36 UTCVendor advisory
- 2026-08-16 17:52 UTCVendor advisory
- 2026-08-16 14:08 UTCVendor advisory
- 2026-08-16 10:25 UTCVendor advisory
- 2026-08-16 06:41 UTCVendor advisory
- 2026-08-16 02:58 UTCVendor advisory
- 2026-08-15 23:15 UTCVendor advisory
- 2026-08-15 19:31 UTCVendor advisory
- 2026-08-15 15:47 UTCVendor advisory
- 2026-08-15 12:03 UTCVendor advisory
- 2026-08-15 08:19 UTCVendor advisory
- 2026-08-15 04:35 UTCVendor advisory
- 2026-08-15 00:51 UTCVendor advisory
- 2026-08-14 21:07 UTCVendor advisory
- 2026-08-14 17:24 UTCVendor advisory
- 2026-08-14 13:40 UTCVendor advisory
- 2026-08-14 09:57 UTCVendor advisory
- 2026-08-14 06:13 UTCVendor advisory
- 2026-08-14 02:30 UTCVendor advisory
- 2026-08-13 22:47 UTCVendor advisory
- 2026-08-13 19:02 UTCVendor advisory
- 2026-08-13 15:18 UTCVendor advisory
- 2026-08-13 11:34 UTCVendor advisory
- 2026-08-13 07:51 UTCVendor advisory
- 2026-08-13 04:08 UTCVendor advisory
- 2026-08-13 00:24 UTCVendor advisory
- 2026-08-12 20:41 UTCVendor advisory
- 2026-08-12 16:57 UTCVendor advisory
- 2026-08-12 13:14 UTCVendor advisory
- 2026-08-12 09:30 UTCVendor advisory
- 2026-08-12 05:46 UTCVendor advisory
- 2026-08-12 02:03 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.