# CVE-2026-76293: Remote Code Execution (RCE) through Splunk Web Manager Extensible Markup Language (XML) in Splunk Enterprise


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-cmhg-c7w9-vh9j

## What is CVE-2026-76293?

CVE-2026-76293 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. 

### Official description

In Splunk Enterprise versions below 10.4.3, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_manager_xml capability could execute arbitrary operating-system commands using the permissions of the user account running Splunk Enterprise by opening the affected configuration in the Splunk Web Manager page. 
The vulnerability is possible because Splunk Web evaluates user-controlled expressions from Manager XML without sufficiently restricting the expression syntax.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-76293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76293 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76293 in the wild and no public exploit code.

Affected product: Splunk 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-76293/ (Markdown: https://insights.sbomify.com/CVE-2026-76293/index.md)
```

## Sources

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

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