CVE-2026-131184: Splunk Enterprise · The software does not neutralize or incorrectly neutralizes user-controllable input before it is
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium · fixed in 10.6.1 : 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.4 |
|---|
- Patch
- Available – fixed in 10.6.1, 10.4.5, 10.2.9 +2
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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 to a fixed release listed under Affected software.
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
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
A fix is available in Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Users should upgrade to these versions or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-131184 is a cross-site scripting (XSS) vulnerability in Splunk Enterprise versions prior to 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It allows a low-privileged user without admin or power roles to inject malicious scripts into private saved search names. When another user interacts with the affected platform alert in the Monitoring Console, the script executes in their browser session, potentially exposing sensitive information or allowing data modification. The issue arises from improper handling of saved-search names in the platform alert workflow. A fix is available in the specified patched versions.