Live › vulnerability › CVE-2026-115708
Elastic Cloud Enterprise follows a symbolic link to a file it should not access, letting a local user reach files outside its intended path. An attacker can bypass authentication and change the configuration of other deployments on the same host.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 15:25 UTC. All times on this page are UTC.
Teams that run Elastic Cloud Enterprise on their own infrastructure with more than one deployment on the same allocator host. Exploitation needs an attacker who can already run code inside a deployment container, such as through custom bundles or plugins, or via another vulnerability. They could then bypass authentication and change other deployments' configuration. Single-deployment-per-allocator setups, and Elastic-managed Cloud, are not named as affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Elastic Cloud Enterprise | vendor | >= 1.0.0, <= 3.8.5; >= 4.0.0, <= 4.2.0 | 3.8.6, 4.2.1 |
3.8.6 (3.x and earlier) or 4.2.1 (4.x)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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).
This page as .md · .json · in your agent: get_signal("CVE-2026-115708")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.