Live › vulnerability › CVE-2026-115713
Elastic Cloud Enterprise mishandles symbolic links before accessing files, letting one deployment be tricked into reading and writing another deployment's data on the same host. An attacker with a foothold on a shared host can reach data belonging to other tenants.
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.
Self-hosted Elastic Cloud Enterprise 4.1.0 to 4.2.0 that has deployments with an Enterprise Search instance. Exploitation needs an attacker who can already run code inside that Enterprise Search container, and then lets them read and write other deployments' data on the same host. ECE 3.x and 4.0.x, ECE without Enterprise Search, and Elastic's hosted cloud can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Elastic Cloud Enterprise | vendor | >= 4.1.0, <= 4.2.0 | 4.2.1 |
4.1.0 through are affected; 3.x and 4.0.x are not4.2.04.2.1 or laterEach 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 unauthorized read and write access to data of other deployments on the same host via Symlink Attack (CAPEC-132).
This page as .md · .json · in your agent: get_signal("CVE-2026-115713")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.