Skip to content
Weekly Signal
Live intelligence Updated 19 Aug 2026 · 20:27 UTC

Elastic, Redhat · Elasticsearch, Fuse

CVE-2015-1427

Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability

Recommended action

Treat this as an immediate remediation priority. Apply updates per vendor instructions.

View response plan
CVSS9.8
EPSS99.9%
KEVYes
ExploitationConfirmed exploitation
PatchPatch or guidance available ↓

Assessment

Why it matters

CISA lists this vulnerability as known to be exploited; exploitation is confirmed; EPSS is 99.9%; technical severity is CVSS 9.8.

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.

Who should care

  • Teams operating Elasticsearch, Fuse
  • Vulnerability and exposure management teams
  • Security operations teams monitoring exploitation activity

Response plan

What I would do

  1. Confirm whether Elasticsearch, Fuse is present in the environment.
  2. Identify affected versions and establish whether vulnerable services are exposed or reachable.
  3. Apply updates per vendor instructions.
  4. Review relevant security telemetry for evidence of attempted or successful exploitation.
  5. Document the remediation decision and track it to verified completion.

Vendor remediation

Patch and remediation links

Use the vendor source below to confirm the correct fixed version, package or mitigation for your affected product.

Technical details

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-284
Affected versions
Elastic Elasticsearch (Start Including: 1.4.0, End Excluding: 1.4.3); Redhat Fuse (Version: 1.0.0)
Published
17 February 2015
Attack vector
Network
Privileges required
None
User interaction
None

Signal timeline

  1. CVE published
  2. Added to CISA KEV
  3. Latest EPSS score: 99.9%
  4. Signal calculated at 85

External references

Live public intelligence This assessment combines public-source evidence. Validate the affected product, version and exposure against your own environment before making a risk decision.