In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium · fixed in 10.4.2 : update Splunk Enterprise when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.2, 10.2.6, 10.0.9 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 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 17 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2, 10.2.6, 10.0.9 or 9.4.14.
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
If you cannot patch yet, restrict the ability to create or share Table Editor datasets to trusted users only. Educate admin users to avoid opening datasets from untrusted sources and be cautious of phishing attempts. Monitor Splunk role assignments to ensure the "power" role is granted only to trusted users. Follow Splunk's guidance on SPL safeguards for risky commands and role definitions to minimize risk.
Description
CVE-2026-76341 is a medium severity vulnerability in Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14. It allows a user with the "power" role to store attacker-controlled Search Processing Language (SPL) in a Table Editor dataset and share it. When an "admin" user opens this dataset, the SPL executes with their permissions, potentially exposing sensitive data and allowing limited data modification. Exploitation requires phishing the admin user to trigger the SPL execution in their browser. The vulnerability arises because the Table Editor does not apply SPL safeguards for risky commands during dataset initialization.