Improper Link Resolution Before File Access ('Link Following') in Elastic Cloud Enterprise (ECE) Leading to Information Disclosure and…
Affects Elastic Cloud Enterprise 4.1.0 through 4.2.0 on hosts running deployments that include an Enterprise Search instance. Fixed in 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 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. A flaw in how it follows symbolic links before accessing files could let an attacker read or modify data belonging 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 unauthorized read and write access to data 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 4.1.0 · through 4.2.0
References 1
discuss.elastic.co
Questions about CVE-2026-115713
What does this mean?
The bug lets ECE follow a link before accessing a file, which can lead to unauthorized read and write access to data of other deployments on the same host.Source: discuss.elastic.co
Am I affected, and how do I check?
Elastic Cloud Enterprise 4.x versions from 4.1.0 up to and including 4.2.0 are in scope, but only for ECE deployments that include an Enterprise Search instance. Check the installed ECE version and whether any deployment includes Enterprise Search.Source: discuss.elastic.co
What should I do about it?
Upgrade Elastic Cloud Enterprise to version 4.2.1, which resolves the issue. No workaround is listed in the facts.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