CVE-2026-131183: SPL Injection through Classic Dashboard in Splunk Enterprise
This Splunk advisory covers CVE-2026-131183 in Splunk Enterprise.
- CVE-2026-131183
Key facts
- Vendor rating
- Medium, CVSS 5.4
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N· base score 5.4, scored by ciscoAttack vector: network. Attack complexity: high. Privileges required: low. User interaction: required. Scope: unchanged. Confidentiality impact: high. Integrity impact: low. Availability impact: none.- Weakness
- CWE-116 The software prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Splunk Enterprise 10.4 before 10.4.5; Splunk Enterprise 10.2 before 10.2.9; Splunk Enterprise 10.0 before 10.0.12 and 1 more below
- Fixed in
- 10.4.5, 10.2.9, 10.0.12 and 1 more below
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who holds the "power" Splunk role could inject arbitrary Search Processing Language (SPL) commands into a Classic Dashboard search.
When another user opens the affected dashboard in Splunk Web, those injected commands execute with the viewing user's permissions, potentially allowing the low-privileged user to access stored credentials and write data to indexes.
The vulnerability is possible because Splunk Enterprise does not correctly escape user-supplied content when it rewrites a search, which lets the rewritten search include additional SPL commands. The vulnerability requires another user to open the dashboard in Splunk Web.
Consequently, a user who holds the "power" Splunk role should not be able to exploit the vulnerability at will. For more information see SPL safeguards for risky commands ( ) and Define roles on the Splunk platform with capabilities ( ) in the Splunk documentation.
Text from the source record.
- Splunk Enterprise 10.4 before 10.4.5
- Splunk Enterprise 10.2 before 10.2.9
- Splunk Enterprise 10.0 before 10.0.12
- Splunk Enterprise 9.4 before 9.4.17
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-131183
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- Upgrade to a fixed release: Splunk Enterprise 10.6.1, Splunk Enterprise 10.4.5, Splunk Enterprise 10.2.9, Splunk Enterprise 10.0.12, Splunk Enterprise 9.4.17.
Support dates for the fixed release lines
- Splunk Enterprise 10.4: support ends
- Splunk Enterprise 10.2: support ends
- Splunk Enterprise 10.0: support ends
- Splunk Enterprise 9.4: support ends
More Splunk advisories
CVE-2026-131197Nov 19, 2026Privilege Escalation through Splunk Web Dashboards in Splunk App for Splunk ObservabilityCVE-2026-131196Nov 19, 2026Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk EnterpriseCVE-2026-131195Nov 19, 2026Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk EnterpriseCVE-2026-131194Nov 19, 2026Stored Cross-Site Scripting (XSS) through Splunk Web Views in Splunk EnterpriseCVE-2026-131193Nov 19, 2026Improper Input Validation through HTTP Event Collector Token Names in Splunk EnterpriseCVE-2026-131192Nov 19, 2026Authentication Bypass through the REST API in Splunk Enterprise
Get an email when Splunk Enterprise publishes the next one.
See Splunk Enterprise's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.