Skip to content
major vulnerability· requires attention

Elastic Cloud Enterprise is widely used; vulnerability enables cross-deployment data disclosure on shared hosts, risking multi-tenant breaches and broad operational impact.

Cloud

CVE-2026-115709

8.2
High
EPSS n/aPatch availableOct 30, 2026

Symlink flaw in Elastic Cloud Enterprise allows cross-deployment data disclosure.

common questions

Is CVE-2026-115709 being exploited?

Not confirmed. CVE-2026-115709 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-115709?

CVE-2026-115709 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-115709?

Yes. A fix has been recorded for CVE-2026-115709. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-115709 affect?

CVE-2026-115709 affects Elastic Cloud Enterprise (ECE) prior to 3.8.6, Elastic Cloud Enterprise (ECE) prior to 4.2.1, Multi-tenant hosts running ECE. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-115709?

Install ECE 3.8.6 / 4.2.1+ now; audit and isolate affected hosts.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Elastic Cloud Enterprise (ECE) prior to 3.8.6Elastic Cloud Enterprise (ECE) prior to 4.2.1Multi-tenant hosts running ECE
impact

Symlink attack allows unauthorized access/read of files from other deployments on the same host, enabling data exfiltration and potential data loss.

action required

Immediate action required

affected versions
Elastic Elastic Cloud Enterprise
  • affected>= 2.6.0 and <= 3.8.5
  • affected>= 4.0.0 and <= 4.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved