CVE-2026-131182: 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 7.6 High · fixed in 10.4.5 : patch Splunk Enterprise soon.
Data as of 19 Nov 2026, 20:18 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.6 |
|---|
- 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:H/A:LExploitation 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
Fixed versions are available: 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. Since the vulnerability requires phishing to exploit, user awareness and phishing prevention measures can reduce risk but do not replace patching. No other vendor advisory mitigation instructions are provided.
Description
CVE-2026-131182 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 user with the "power" Splunk role to store malicious Search Processing Language (SPL) code in a shared dashboard. When another user opens this dashboard, the malicious SPL runs with their permissions, potentially accessing or modifying their data and disrupting availability. Exploitation requires phishing to trick the victim into initiating a request in their browser. The vulnerability arises because Splunk Enterprise does not preserve quoted search argument boundaries during dashboard search processing.