CVE-2026-76255: Splunk Enterprise · The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium · fixed in 10.4.1 : update Splunk Enterprise when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.1, 10.2.6, 10.0.8 +1
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 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 15 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.1, 10.2.6, 10.0.8 or 9.4.13.
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
Splunk has released fixed versions 10.4.1, 10.2.6, 10.0.8, and 9.4.13 that address this vulnerability. Users should upgrade to these or later versions to remediate the issue. Additionally, reviewing and enforcing strict role definitions and capabilities in Splunk can reduce risk. The vulnerability requires phishing and user interaction, so user awareness and training may also help mitigate exploitation risk.
Description
CVE-2026-76255 is a vulnerability in Splunk Enterprise versions prior to 10.4.1, 10.2.6, 10.0.8, and 9.4.13 where insufficient authorization checks allow a non-admin or non-power user to trick another user into executing arbitrary SPL commands via the Data Model Editor. This occurs because Splunk Web does not apply safeguards for risky commands during certain base searches. Exploitation requires phishing the affected user to initiate a request in their browser. The vulnerability can lead to unauthorized data access and impact system integrity.