CVE-2026-131179: Splunk Enterprise · The software constructs all or part of a command, data structure, or record using
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
Apply the official fixes by upgrading to Splunk Enterprise versions 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later. Since fixed versions are available, upgrading is the recommended remediation. No other specific mitigations are indicated in the advisory. Limit the assignment of the "power" role to trusted users to reduce risk.
Description
CVE-2026-131179 is a high-severity 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" role to inject attacker-controlled Search Processing Language (SPL) into shared dashboards. When another user views the dashboard, the malicious SPL executes with the viewer's permissions, potentially exposing stored credentials, modifying indexed data, and impacting availability. Exploitation requires phishing to trick a user into triggering the malicious SPL via their browser. The vulnerability arises from insufficient neutralization of special elements in search filter values during search job construction. Fixed versions are available.