# CVE-2026-76341: Risky Commands Safeguards Bypass through Table Editor Dataset Initial Data in Splunk Enterprise > A power user can bypass SPL safeguards to execute risky commands with admin privileges via a shared dataset, exposing data. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 19 Aug 2026 - **Updated:** 26 Aug 2026 - **Also known as:** GHSA-fccc-vrj3-v737 ## What is CVE-2026-76341? CVE-2026-76341 is a medium-severity vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a Table Editor dataset and share the dataset. A user who holds the "admin" Splunk role triggers the SPL when that user opens the dataset in the Table Editor. The SPL runs using the permissions of the second user and could expose all relevant data and modify limited data on the search head. The vulnerability is possible because the Table Editor does not apply SPL safeguards for risky commands when it prepares the dataset initial data. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who holds the "power" Splunk role should not be able to exploit the vulnerability at will. For more information see Define initial data for a new table dataset (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/9.4/create-and-edit-table-datasets/define-initial-data-for-a-new-table-dataset), SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands), and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-76341? It affects 1 product. Products: Splunk Splunk. ## How do I fix CVE-2026-76341? No fix has been published for CVE-2026-76341 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-76341 being exploited? There is no known exploitation of CVE-2026-76341 in the wild and no public exploit code. ## Other vulnerabilities in Splunk Splunk - [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild) - [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8) - [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8) - [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8) - [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-76341 and fix it if it is affected. What it is: CVE-2026-76341 is a medium-severity vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-76341 in the wild and no public exploit code. Affected product: Splunk Splunk. 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-76341/ (Markdown: https://insights.sbomify.com/CVE-2026-76341/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76341 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76341 - OSV: https://osv.dev/vulnerability/CVE-2026-76341 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-76341/ Summaries are generated and may contain mistakes; the official description above is the record.