Splunk Enterprise data access via SPL injection in classic dashboards
- Exploited
- No known exploitation
- Fix
- Fixed in 10.4.5, 10.2.9, 10.0.12, 9.4.17
- Who is exposed
- Specific setups only
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
Original 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 (help.splunk.com/
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
“In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17”
What to do
Check whether your setup matches what the bug needs.
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 A shared Classic Dashboard must be crafted to run the injected SPLUpgrade to a fixed version: 10.4.5, 10.2.9, 10.0.12, 9.4.17.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
- Splunk Splunk EnterpriseFrom 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
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 7.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1103 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131178 |
| Record | NVD · CVE-2026-131178 |
Questions about CVE-2026-131178
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: cve.now feed data
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: advisory.splunk.com
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: cve.now feed data
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: advisory.splunk.com
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: advisory.splunk.com
Related
- CVE-2026-131236SPL Injection through Splunk Web Workflow Actions in Splunk Enterprise Security
- CVE-2026-131218SPL Injection through the Mission Control REST API in Splunk Enterprise Security
- CVE-2026-131239SPL Injection through the System Update Status Report in Splunk Enterprise Security
- CVE-2026-131222Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security
- CVE-2026-131238Search Processing Language (SPL) Injection through the Secure Sockets Layer Search Dashboard in Splunk Enterprise Security
- CVE-2026-131232SPL Injection through the Vulnerability Scan Details Splunk Web Dashboard in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.