CVE-2026-76312: Splunk Enterprise · The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical · fixed in 10.4.1 : patch Splunk Enterprise as a priority.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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.9 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LExploitation 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 18 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.1, 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
A fix is available in Splunk Enterprise versions 10.4.1, 10.2.6, 10.0.9, and 9.4.14. Users should upgrade to these or later versions to remediate the vulnerability. Refer to Splunk's official documentation on additional configuration for embedded reports and embedding scheduled reports for further guidance. No other mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-76312 is a critical vulnerability in Splunk Enterprise versions prior to 10.4.1, 10.2.6, 10.0.9, and 9.4.14. It allows an unauthenticated user who can read the HTML source of a page embedding a Splunk report to access sensitive session material. This exposure enables unauthorized access to all relevant data and can impact system integrity. The root cause is improper enforcement of authorization boundaries in the dispatch archive download path, which includes sensitive session data in archived search-job data.