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 — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 100%CVSS: 9.8Exploit: cisa kev · ssvc active · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

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.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100CISA SSVC

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 computed
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
100%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 17, 2015

Last Modified

April 22, 2026

Advisory Details (7)

Auto-updated Oct 8, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: redhat.
generic

Packet Storm

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

Packet Storm

http://packetstormsecurity.com/files/130368/Elasticsearch-1.3.7-1.4.2-Sandbox-Escape-Command-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
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:0868
generic🔴 Active Exploitation

CVE-2015-1427 - PSIRT.COM

http://www.securityfocus.com/bid/72585
generic

SecurityFocus

http://www.securityfocus.com/archive/1/534689/100/0/threaded

Vendor 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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
org.elasticsearch:elasticsearch1.4.0, 1.4.1, 1.4.2
  • every version up to 1.3.8: fixed in 1.3.8
  • 1.4.0 up to 1.4.3: fixed in 1.4.3
—

Data Freshness Timeline

(refreshed 47× in last 7d / 210× 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 937 total refreshes for this CVE.

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

  • 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 ↗
  • 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 ↗
  • Nucleihttp/cves/2015/CVE-2015-1427.yaml
    First seen Jan 1, 2015

    ElasticSearch - Remote Code Execution

    Open source ↗

Related CVEs(same product + same vendor)

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 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 attention. A fix is available. Apply it.
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 affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2015-1427?
A fix for CVE-2015-1427 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2015-1427 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs