Skip to main content
VulnerabilityPublished Updated

CVE-2025-37736: Elastic Cloud Enterprise (ECE) · Incorrect Authorization

Affects Elastic Cloud Enterprise (ECE)Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Elastic Elastic Cloud Enterprise (ECE)Affected
  • =3.8.0
  • =4.0.0
Fixed in–

AI-suggested

Immediate mitigation involves restricting readonly user access and monitoring API usage for suspicious activity. Organizations should implement strict network segmentation and access controls to limit exposure of ECE management interfaces. Until patches are available, consider disabling or restricting the affected API endpoints via proxy or firewall rules. Employ robust logging and alerting on service account and user management API calls to detect unauthorized attempts. Review and minimize the assignment of readonly roles to only trusted personnel and systems. When patches are released by Elastic, apply them promptly. Additionally, conduct regular audits of service accounts, API keys, and user privileges to identify and remediate any unauthorized changes. Employ multi-factor authentication and strong credential management to reduce risk of credential compromise that could be leveraged in conjunction with this vulnerability.

Description

Improper Authorization in Elastic Cloud Enterprise can lead to Privilege Escalation where the built-in readonly user can call APIs that should not be allowed. The list of APIs that are affected by this issue is: post:/platform/configuration/security/service-accounts delete:/platform/configuration/security/service-accounts/{user_id} patch:/platform/configuration/security/service-accounts/{user_id} post:/platform/configuration/security/service-accounts/{user_id}/keys delete:/platform/configuration/security/service-accounts/{user_id}/keys/{api_key_id} patch:/user post:/users post:/users/auth/keys delete:/users/auth/keys delete:/users/auth/keys/_all delete:/users/auth/keys/{api_key_id} delete:/users/{user_id}/auth/keys delete:/users/{user_id}/auth/keys/{api_key_id} delete:/users/{user_name} patch:/users/{user_name}

References

Community reviews

Loading reviews…