CVE-2026-76259: Splunk Enterprise · The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 10.4.2 : patch Splunk Enterprise soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% 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 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation 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 to a fixed release listed under Affected software.
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
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
A fix is available in Splunk Enterprise versions 10.4.2, 10.2.6, 10.0.9, 9.4.13, and 9.3.14. Users should upgrade to these or later versions to remediate the vulnerability. No information indicates alternative mitigations or that the vulnerability is already mitigated without patching.
Description
CVE-2026-76259 is a high-severity vulnerability in Splunk Enterprise for Windows that affects versions prior to 10.4.2, 10.2.6, 10.0.9, 9.4.13, and 9.3.14. A local user with access to the Windows host can bind to the management port before Splunk Enterprise starts, intercept authentication tokens from child processes, and use these tokens to compromise data and system integrity. This occurs because the management-port listener does not enforce exclusive address binding protections before service startup.