Improper Link Resolution Before File Access ('Link Following') in Elastic Cloud Enterprise (ECE) Leading to Authentication Bypass
Affects Elastic Cloud Enterprise 1.0.0 through 3.8.5 and 4.0.0 through 4.2.0 on installations running more than one deployment on the same allocator host. 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), a platform for deploying and managing Elastic stack clusters, is affected by this vulnerability. An attacker who can abuse symbolic links on the host could bypass authentication and make unauthorized configuration changes to other deployments running 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 authentication bypass and unauthorized changes to the configuration of 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 1.0.0 · through 3.8.5; From 4.0.0 · through 4.2.0
References 1
Questions about CVE-2026-115708
What does this mean?
A link-following flaw in ECE lets an attacker who can run code inside an Elasticsearch deployment container cause an authentication bypass and make unauthorized configuration changes to other deployments on the same host.Source: discuss.elastic.co
Am I affected, and how do I check?
ECE versions 1.0.0 through 3.8.5 and 4.0.0 through 4.2.0 are listed as affected, and the issue matters only on installations that run more than one deployment on the same allocator host. Check the installed ECE version and whether several deployments share an allocator host.Source: discuss.elastic.co
What should I do about it?
Upgrade to ECE 3.8.6 or 4.2.1, the versions that resolve the issue. The facts list no workaround.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