CVE-2026-131183: Splunk Enterprise · The software prepares a structured message for communication with another component, but encoding or
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium · fixed in 10.4.5 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 20:19 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.5, 10.2.9, 10.0.12 or 9.4.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Upgrade Splunk Enterprise to version 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later, where this vulnerability is fixed. Until upgraded, restrict the assignment of the "power" role to trusted users only and educate users to be cautious when opening dashboards from untrusted sources. Follow Splunk's official guidance on SPL safeguards for risky commands and role capability definitions to minimize risk.
Description
CVE-2026-131183 is a vulnerability in Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It allows a low-privileged user with the "power" Splunk role to inject arbitrary Search Processing Language (SPL) commands into a Classic Dashboard search. When another user opens the affected dashboard in Splunk Web, the injected commands execute with the viewing user's permissions, potentially exposing stored credentials and allowing data writes to indexes. The vulnerability arises from improper escaping of user-supplied content during search rewriting. Exploitation requires another user to open the dashboard, limiting direct exploitation by the low-privileged user.