In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could trick a user
Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium · fixed in 10.4.5 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 22:19 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/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 19 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
A fix is available in Splunk Enterprise versions 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. Until patched, users should be cautious of phishing attempts that could trick them into opening malicious links.
Description
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated attacker can trick an active Splunk Web user into running arbitrary SPL searches via a crafted link. This can potentially expose stored credentials and indexed data. Exploitation requires phishing the user to open the malicious link. The vulnerability arises from improper neutralization of user-controlled data when generating SPL searches for field reports.