CVE-2025-37729: Elastic Cloud Enterprise (ECE) · Template Injection
Affects Elastic Cloud Enterprise (ECE)Source CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Elastic Elastic Cloud Enterprise (ECE) | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-37729, organizations should implement the following specific measures: 1) Immediately restrict administrative access to Elastic Cloud Enterprise to only trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA). 2) Monitor and audit all admin activities within ECE for unusual or unauthorized template modifications or command executions. 3) Apply principle of least privilege by reviewing and minimizing the number of users with admin rights. 4) Since no official patches are currently available, consider deploying compensating controls such as network segmentation to isolate ECE management interfaces from general network access. 5) Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious template injection patterns. 6) Prepare for rapid patch deployment by subscribing to Elastic’s security advisories and testing updates in staging environments. 7) Conduct regular security training for administrators on secure template usage and the risks of injection attacks. 8) Review and sanitize any user-generated input that might be processed by Jinjava templates to prevent injection vectors. These targeted actions go beyond generic advice and focus on reducing the attack surface and detecting exploitation attempts until a patch is released.
Description
Improper neutralization of special elements used in a template engine in Elastic Cloud Enterprise (ECE) can lead to a malicious actor with Admin access exfiltrating sensitive information and issuing commands via a specially crafted string where Jinjava variables are evaluated.