CVE-2026-131194: 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 4.6 Medium · fixed in 10.4.4 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 20:07 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 4.6 |
|---|
- Patch
- Available – fixed in 10.4.4, 10.2.8, 10.0.11 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/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.4, 10.2.8, 10.0.11 or 9.4.16.
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 patches by upgrading to Splunk Enterprise versions 10.4.4, 10.2.8, 10.0.11, or 9.4.16 or later, where this vulnerability is fixed. No other specific mitigations are indicated. Ensure that only trusted users are assigned the "power" role to limit exposure until patched.
Description
CVE-2026-131194 is a cross-site scripting (XSS) vulnerability in Splunk Enterprise versions prior to 10.4.4, 10.2.8, 10.0.11, and 9.4.16. It allows a low-privileged user with the "power" role to inject malicious JavaScript into a Splunk Web view. When another authenticated user opens the affected view, the injected script executes in their browser session. This occurs because Splunk Web does not properly validate user-controllable content in view definitions before rendering.