Skip to main content

Elastic Cloud Enterprise EUVDEUVD-2026-112919

| CVE-2026-115706 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-29 elastic GHSA-fmgj-xvwq-2gqq
6.8
CVSS 3.1 · Vendor: elastic
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain control of any host in ECE installation
  2. Delivery
    Abuse user-controlled key to request reserved credentials
  3. Exploit
    Obtain credentials of higher platform role
  4. Execution
    Authenticate to ECE control plane
  5. Impact
    Seize control of control plane and managed deployments

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

The attacker must already control at least one host within the ECE installation; per the description, any such host can abuse the user-controlled key to retrieve credentials reserved for other platform roles. This is the gating precondition: it is NOT remotely exploitable by an unauthenticated internet attacker, matching the vendor vector AV:A (adjacent, within the ECE network) and PR:H (an existing privileged/host foothold is required). No user interaction is needed (UI:N) and no special non-default configuration is called out in the advisory, so default ECE installations on affected versions are in scope. The practical limiter is therefore the host-control prerequisite, which confines realistic exploitation to insiders, co-tenants, or an attacker who has already breached an ECE host; the payoff, once that bar is met, is full control-plane and managed-deployment compromise.

Impact

This is a medium-severity (CVSS 6.8) authorization-bypass issue whose signals point to a contained-but-serious insider/lateral-movement risk rather than a mass-exploitation emergency. The vendor CVSS vector (AV:A/AC:L/PR:H) already encodes the dominant limiting factor: the attacker must control some host inside the ECE installation (PR:H) and operate from the adjacent ECE network (AV:A), so this is not internet-facing, unauthenticated, wormable exploitation. Against that, the impact is high across confidentiality, integrity and availability (C:H/I:H/A:H) because the obtained credentials grant full control of the ECE control plane and every deployment it manages - effectively a full-platform compromise once the precondition is met. The vuln.today decision label is 'this_month', which aligns with that profile: patch promptly but it is not flagged act_now/emergency. Key data is MISSING and should not be presented as reassurance: no EPSS exploitation-probability score is provided, the vulnerability is NOT listed in CISA KEV, and no public exploit or PoC reference is provided (only a vendor advisory). The net read is a genuinely high-impact privilege-escalation path gated behind an existing foothold - prioritize for environments where ECE host boundaries are part of the trust model, but it is not a drop-everything internet-exposed flaw.

Exploit ScenarioDerived

An attacker who has already gained control of any single host within an ECE installation (for example via a separate compromise or a malicious/over-privileged tenant on shared infrastructure) abuses the user-controlled-key authorization flaw to obtain credentials reserved for higher platform roles. Using those credentials, the attacker pivots to full control of the ECE control plane and all managed deployments. No public exploit identified at time of analysis; the attack requires an existing foothold (PR:H) and adjacent-network position (AV:A).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 29, 2026

Elastic Cloud Enterprise (ECE) installations on versions prior to the fixed 3.8.6 and 4.2.1 releases allow an attacker who already controls any host in the installation to obtain credentials reserved for other platform roles, escalating from a host foothold to full control of the ECE control plane and every deployment it manages. The flaw is an authorization bypass through a user-controlled key (CWE-639), meaning the platform trusts a caller-supplied identifier when deciding which role's credentials to return. The vendor vector (CVSS:3.1/AV:A/AC:L/PR:H/UI:N) confirms the meaningful limiter: exploitation requires an existing privileged position adjacent to the ECE network, so this is an insider, co-tenant or post-breach lateral-movement risk (medium severity, CVSS 6.8) rather than a mass internet-exploitation event. No public exploit code or CISA KEV entry is associated with this CVE at time of analysis; prioritization is 'this_month'.

RemediationAI

Upgrade Elastic Cloud Enterprise to 3.8.6 or 4.2.1 as applicable to your release branch; these are the fixed versions named in the vendor advisory ESA-2026-211 (https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260), which is also the authoritative source for any additional instructions or residual impacted-version details. Because the vulnerability yields credentials belonging to other ECE platform roles, treat any affected installation as potentially compromised: rotate ECE platform and role credentials and audit control-plane and deployment access logs after patching, since patching alone does not invalidate credentials already obtained. Until the upgrade is complete, the practical compensating control is network segmentation - restrict which hosts can reach the ECE control-plane APIs to the minimum set of trusted management hosts, using firewall rules or a management VLAN, with the trade-off that legitimate operators must work from those hosts and any already-compromised allowed host retains the ability to exploit the flaw. Strong host-level controls on ECE nodes (limiting who can obtain a foothold, hardening administrator access, monitoring for unexpected credential use) reduce exposure to the host-control precondition, but they do not remove the authorization bypass itself; the fixed release is the only complete remediation identified in the available sources.

Affected VersionsENISA

Elastic Cloud Enterprise 4.0.0 ≤4.2.0
Elastic Cloud Enterprise 1.0.0 ≤3.8.5

Affected Packages

euvd elastic_cloud_enterprise no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Elastic Cloud Enterprise is the orchestration and control-plane layer that provisions, configures and manages Elasticsearch (and related) deployments on behalf of tenants. The root cause class is CWE-639, authorization bypass through user-controlled key: an endpoint that resolves a resource or credential by an identifier taken from the request does not verify that the requester is entitled to the role being resolved, so changing the key yields another platform role's material. Because ECE's own role credentials are what protect the control plane, possession of a higher-privileged role's credentials collapses the boundary between the managed host and the orchestrator, giving an attacker command of deployments across tenants. The trigger conditions and the specific endpoint are not described in the available sources. The vendor's CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U vector and the independent assessment agree on the essentials - adjacent-network attack vector, no user interaction, and a high-privilege prerequisite - while the independent assessment scores scope as changed (S:C) and impact as full confidentiality, integrity and availability (C:H/I:H/A:H), reflecting that compromise escapes the initially compromised host into the control plane. No non-default configuration is called out, so default ECE installations on affected versions are exposed once the host-control precondition is met.

Know when Elastic Cloud Enterprise gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (elastic) PRIMARY 6.8 MEDIUM
AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.4 HIGH

Requires an existing host foothold (PR:H) on the adjacent ECE network (AV:A); scope is changed (S:C) because compromise extends from the authorization component to the control plane and separately-managed deployments, with full C/I/A impact.

3.1 AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (elastic).

CVSS VectorVendor: elastic

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Authorization Bypass Through User-Controlled Key (CWE-639) in Elastic Cloud Enterprise (ECE) can lead to privilege escalation via Privilege Abuse (CAPEC-122). An attacker who controls any host in an ECE installation can obtain credentials that are reserved for other platform roles. These credentials can give the attacker full control of the ECE control plane and of the deployments that it manages.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
niche self-hosted Elastic orchestration platform, limited and specialized enterprise footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2024-37282 CRITICAL
9.8 Jun 28

It was identified that under certain specific preconditions, an API key that was originally created with a specific priv

CVE-2025-37736 HIGH
8.8 Nov 07

Improper Authorization in Elastic Cloud Enterprise can lead to Privilege Escalation where the built-in readonly user can

CVE-2026-115709 HIGH
8.2 Oct 29

Elastic Cloud Enterprise (ECE) instances that host multiple deployments on a single multi-tenant host are exposed to cro

CVE-2026-115713 HIGH
7.5 Oct 29

Elastic Cloud Enterprise (ECE) hosts that have not applied the 4.2.1 security update are exposed to a symlink-following

CVE-2023-31418 HIGH
7.5 Oct 26

An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. Rated high severity (CV

CVE-2018-3828 HIGH
7.5 Sep 19

Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 contain an information exposure vulnerability. Rated high severit

CVE-2025-37729 HIGH
7.2 Oct 13

Server-side template injection (SSTI) in Elastic Cloud Enterprise (ECE) allows an authenticated Administrator to execute

CVE-2026-115708 HIGH
7.2 Oct 29

Elastic Cloud Enterprise (ECE) 3.x before 3.8.6 and 4.x before 4.2.1 can allow a local, highly privileged attacker to ex

CVE-2022-23715 MEDIUM
6.5 Aug 25

A flaw was discovered in ECE before 3.4.0 that might lead to the disclosure of sensitive information such as user passwo

CVE-2026-115711 MEDIUM
6.4 Oct 29

Elastic Cloud Enterprise stores runtime information about its platform service containers - including secrets drawn from

CVE-2026-115707 MEDIUM
6.4 Oct 29

Privilege escalation in Elastic Cloud Enterprise lets an attacker who already controls a host in an ECE installation lev

CVE-2018-3825 MEDIUM
5.9 Sep 19

In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 a default master encryption key is used in the process of gran

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy