Quick answers
- Is CVE-2026-115711 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115711 being exploited in the wild.
- How severe is CVE-2026-115711?
- Medium severity, with a CVSS score of 6.4, published 29 October 2026.
- Which products and versions are affected?
- Elastic Cloud Enterprise 1.0.0 through 3.8.5, 4.0.0 through 4.2.0.
- Is there a fix for CVE-2026-115711?
- Yes: fixed in Cloud Enterprise 3.8.6, 4.2.1. Until then: Revoke persistent role tokens that are no longer needed. Use ephemeral role tokens for adding new hosts to the installation instead of persistent role tokens. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115711 attacked?
- It is attacked from the adjacent network or with local access.
- Am I affected by CVE-2026-115711?
- Check whether you run Elastic Cloud Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Cloud Enterprise 3.8.6, 4.2.1
Revoke persistent role tokens that are no longer needed. Use ephemeral role tokens for adding new hosts to the installation instead of persistent role tokens.
Technical details
Sensitive information including role tokens is stored in runtime data files for platform service containers at a location accessible to lower-privileged platform components. An attacker with access to internal ECE platform services can retrieve these secrets and use role tokens to add unauthorized hosts with elevated privileges. Exploitation requires network access to ECE platform services or administrative access to an ECE host.
Affected products
- Elastic Cloud Enterprise 1.0.0 through 3.8.5, 4.0.0 through 4.2.0
Timeline
- 2026-10-29: disclosed