# CVE-2026-115707: Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) in Elastic Cloud Enterprise (ECE) can lead to priv


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-j27j-r2hf-x7q7

## What is CVE-2026-115707?

CVE-2026-115707 is a medium-severity vulnerability in Elastic Cloud Enterprise, published on 29 Oct 2026. 

### Official description

Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) in Elastic Cloud Enterprise (ECE) can lead to privilege escalation via Retrieve Embedded Sensitive Data (CAPEC-37). After the ECE certificate rotation procedure runs, data that it retains contains platform credentials and certificate authority private keys, and lower-privileged platform components can read this data. An attacker who controls any host in the installation can use this data to get full control of the ECE control plane and of the deployments that it manages.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

## Which versions are affected by CVE-2026-115707?


## How do I fix CVE-2026-115707?

No fix has been published for CVE-2026-115707 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115707 being exploited?

There is no known exploitation of CVE-2026-115707 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115707 and fix it if it is affected.

What it is: CVE-2026-115707 is a medium-severity vulnerability in Elastic Cloud Enterprise, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115707 in the wild and no public exploit code.

Affected product: Elastic Cloud Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115707/ (Markdown: https://insights.sbomify.com/CVE-2026-115707/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115707
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115707
- OSV: https://osv.dev/vulnerability/CVE-2026-115707

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115707/
Summaries are generated and may contain mistakes; the official description above is the record.