In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who does not
Source GCVE Database
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, 22:55 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 19 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
The vulnerability affects specific versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Users should upgrade to these versions or later where the issue is fixed. Until patched, restrict low-privileged users from creating or modifying saved searches that could be used in platform alerts, and limit access to the Monitoring Console to trusted users only.
Description
Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where a low-privileged user can inject malicious scripts into the name of a private saved search. When another user with higher privileges interacts with the affected platform alert in the Monitoring Console, the script executes in their browser session. This can lead to unauthorized viewing or modification of sensitive data within Splunk Enterprise. The issue arises from improper handling of saved-search names in the platform alert workflow.