Splunk Enterprise SPL injection in shared dashboards
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, or 9.4.17 are affected. Fixed in 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Splunk recommends 10.6.1.
- 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 shared dashboards. An attacker who holds the "power" role can reach it remotely after logging in with low privileges, but only by tricking a logged-in user into initiating a request in their browser; the malicious search then runs with that user's permissions, letting the attacker access or modify that user's data and disrupt the product's availability.
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 store malicious Search Processing Language (SPL) in a shared dashboard. The malicious SPL could run using the permissions of the user who opened the dashboard and could access or modify data available to that user and disrupt Splunk Enterprise availability. The vulnerability is possible because Splunk Enterprise does not preserve quoted search argument boundaries when it processes a dashboard search. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker, a user who holds the "power" Splunk role, should not be able to exploit the vulnerability at will.
Who should check
Teams running Splunk Enterprise below the fixed releases where users with the power role share dashboards, and the users who open those 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, or 9.4.17 Splunk Enterprise does not preserve quoted search argument boundaries when processing a dashboard searchUpgrade 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-131182 (SPL Injection through Shared Dashboards 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-131182 (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, or 9.4.17 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- Splunk Enterprise does not preserve quoted search argument boundaries when processing a dashboard search (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-131182 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131182 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-131182
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-131182
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-131182"}.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-131182 |
| Record | NVD · CVE-2026-131182 |
Questions about CVE-2026-131182
Is CVE-2026-131182 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?
Splunk Enterprise does not preserve quoted search argument boundaries when it processes a dashboard search. Malicious SPL stored in a shared dashboard runs with the permissions of the user who opens it, so it can access or modify that user's data and disrupt Splunk Enterprise availability.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-131182?
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, or 9.4.17 are affected, covering the 9.4, 10.0, 10.2, and 10.4 lines before their fixed releases. Check the installed Splunk Enterprise version against these ranges.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-131182?
Upgrade to 10.4.5, 10.2.9, 10.0.12, or 9.4.17, the fixed version for the release line in use. Splunk recommends upgrading to 10.6.1 or higher.
Source: advisory.splunk.com, cve.org
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.