CVE-2026-76266: 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 7.7 High · fixed in 10.4.3 : patch Splunk Enterprise soon.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.3, 10.2.7, 10.0.10 +1
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 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 24 Oct 2026.
What to do
Upgrade Splunk Enterprise to 10.4.3, 10.2.7, 10.0.10 or 9.4.15.
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 local user access to the Splunk Enterprise user account and avoid performing Linux package upgrades on affected versions if possible.
Description
CVE-2026-76266 is a privilege escalation vulnerability in Splunk Enterprise on Linux. It affects versions prior to 10.4.3, 10.2.7, 10.0.10, and 9.4.15. A local user with the ability to run commands as the Splunk Enterprise user can manipulate the installation content. When a Linux package upgrade is performed, this can lead to execution of attacker-controlled commands with root privileges. The vulnerability arises because the package maintainer script trusts existing installation content during upgrades. Exploitation requires a package upgrade after the local user modifies the installation. This vulnerability allows unauthorized privilege escalation from a local user with limited privileges to root.