CVE-2026-131180: 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 6.3 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 | 6.3 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/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
Splunk has released fixes in versions 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Users should upgrade to these or later versions to remediate the vulnerability. Additionally, reviewing and restricting the assignment of the 'power' role and following Splunk's SPL safeguards for risky commands can help mitigate risk.
Description
CVE-2026-131180 affects Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17. A user with the 'power' Splunk role can create and share dashboards containing attacker-controlled Search Processing Language (SPL) that executes with the permissions of the user viewing the dashboard. This vulnerability arises from improper escaping of field names in searches using the rename command, potentially allowing exposure of stored credentials and unauthorized data writes to an index.