CVE-2015-1427

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
100.0%
KEV
⚠ Exploited

Published

February 17, 2015

Last Modified

April 22, 2026

Advisory Details (6)

Auto-updated May 12, 2026
Patch available. Sources: redhat.
generic

Packet Storm

http://packetstormsecurity.com/files/130784/ElasticSearch-Unauthenticated-Remote-Code-Execution.html
generic

Product Security at Elastic | Elastic

https://www.elastic.co/community/security/
generic

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/100850
redhat Patch Available
https://access.redhat.com/errata/RHSA-2017:0868
generic
http://www.securityfocus.com/bid/72585
generic
http://www.securityfocus.com/archive/1/534689/100/0/threaded

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2017-04-03redhat

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:elasticsearch1.4.0, 1.4.1, 1.4.21.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 94× in last 7d / 399× 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 594 total refreshes for this CVE.

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

    Elasticsearch 1.4.0 < 1.4.2 Remote Code Execution exploit and vulnerable container

    Open source ↗
  • Exploit-DBEDB-36415✓ verified
    First seen Mar 16, 2015

    ElasticSearch - Search Groovy Sandbox Bypass (Metasploit)

    Open source ↗
  • Exploit-DBEDB-36337✓ verified
    First seen Mar 11, 2015

    ElasticSearch - Remote Code Execution

    Open source ↗
  • Metasploitexploit/multi/elasticsearch/search_groovy_script✓ verified
    First seen Feb 11, 2015

    ElasticSearch Search Groovy Sandbox Bypass

    Open source ↗
  • Nucleihttp/cves/2015/CVE-2015-1427.yaml
    First seen Jan 1, 2015

    ElasticSearch - Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2015-1427?
CVE-2015-1427 is a critical vulnerability published on February 17, 2015. 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.
When was CVE-2015-1427 disclosed?
CVE-2015-1427 was first published in the National Vulnerability Database on February 17, 2015, 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-2015-1427 actively exploited?
Yes. CISA added CVE-2015-1427 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-2015-1427?
CVE-2015-1427 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2015-1427?
CVE-2015-1427 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-2015-1427?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-1427, 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-2015-1427

Explore →

Is Your Infrastructure Affected by CVE-2015-1427?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs