{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-115706 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-115706 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-115706 is a medium-severity vulnerability in Elastic Cloud Enterprise, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-115706 and fix it if it is affected.\n\nWhat it is: CVE-2026-115706 is a medium-severity vulnerability in Elastic Cloud Enterprise, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-115706 in the wild and no public exploit code.\n\nAffected product: Elastic Cloud Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-115706/ (Markdown: https://insights.sbomify.com/CVE-2026-115706/index.md)","id":"CVE-2026-115706","markdown":"https://insights.sbomify.com/CVE-2026-115706/index.md","name":"CVE-2026-115706","record":{"aliases":["GHSA-fmgj-xvwq-2gqq"],"analysis":null,"analysis_generated_by":null,"assigner":"elastic","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Authorization Bypass Through User-Controlled Key in Elastic Cloud Enterprise (ECE) Leading to Privilege Escalation","id":"CVE-2026-115706","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) in Elastic Cloud Enterprise (ECE) can lead to priv","id":"CVE-2026-115707"},"packages":[],"prev":{"headline":"SSRF allowlist bypass via percent-encoded bracketed IPv6 or trailing-dot IP literal in hackney","id":"CVE-2026-115700"},"products":["Elastic Cloud Enterprise"],"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["Elastic"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-115706/"}