Improper Link Resolution Before File Access ('Link Following') in Elastic Cloud Enterprise (ECE) Leading to Information Disclosure and Data Loss
Affects Elastic Cloud Enterprise 2.6.0 through 3.8.5 and 4.0.0 through 4.2.0. CVSS scores it 8.2 (high); no vendor severity is given. Fixed in 3.8.6 and 4.2.1.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.8.6, 4.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Elastic Cloud Enterprise (ECE) is affected by a flaw that allows improper handling of symbolic links when accessing files. This could let an attacker expose or delete data belonging to other deployments on the same host.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Improper Link Resolution Before File Access ('Link Following') (CWE-59) in Elastic Cloud Enterprise (ECE) can lead to unauthorized disclosure and loss of data belonging to other deployments on the same host via Symlink Attack (CAPEC-132).
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Elastic Elastic Cloud Enterprise
From 2.6.0 · through 3.8.5; From 4.0.0 · through 4.2.0
References 1
Questions about CVE-2026-115709
What does this mean?
A flaw in how ECE resolves links before accessing files can let code running inside an Elasticsearch deployment container reach files belonging to other deployments on the same host. The result is unauthorized disclosure and loss of that data.Source: discuss.elastic.co
Am I affected, and how do I check?
ECE 2.x and 3.x from 2.6.0 up to and including 3.8.5, and ECE 4.x from 4.0.0 up to and including 4.2.0. The issue requires code to be able to run inside an Elasticsearch deployment container, for example through custom bundles or plugins. To check, compare the installed ECE version against these ranges.Source: discuss.elastic.co
What should I do about it?
Upgrade to ECE 3.8.6 if on the 3.x line, or to ECE 4.2.1 if on the 4.x line. The advisory states the issue is resolved in these versions.Source: discuss.elastic.co
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data