CVE-2026-76342: 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 store risky Search Processing
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
Until patched, restrict the assignment of the "power" role to trusted users only and educate admin users to avoid opening untrusted datasets. Review and apply SPL safeguards as recommended by Splunk documentation on risky commands and role capabilities.
Description
In certain versions of Splunk Enterprise prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user with the "power" role can store risky Search Processing Language (SPL) commands in a Table Editor dataset and share it. When a user with the "admin" role opens this dataset, the stored commands execute with the admin's permissions, potentially exposing sensitive data and modifying lookup files. This occurs because the Table Editor does not apply SPL safeguards to the field-summary search during the Initial Data step. Exploitation requires phishing an admin user to open the crafted dataset in their browser. The vulnerability is rated medium severity with a CVSS score of 5.4.