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


- **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-j3hp-3xxc-r2mw

## What is CVE-2026-115711?

CVE-2026-115711 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 credential disclosure via Retrieve Embedded Sensitive Data (CAPEC-37). ECE stores runtime information about platform service containers in a location that lower-privileged platform components can read, and this information includes secrets from the container configuration. An attacker with access to the internal ECE platform services can obtain these secrets, which include role tokens. A role token can let the attacker add an unauthorized host to the installation with the roles of that token.

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

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


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

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

## Is CVE-2026-115711 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115711 is a medium-severity vulnerability in Elastic Cloud Enterprise, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115711 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-115711/ (Markdown: https://insights.sbomify.com/CVE-2026-115711/index.md)
```

## Sources

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

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