Splunk Enterprise: Improper Privilege Management
CVE-2026-76266 is a high-severity improper privilege management vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, but only if a user takes part, for example by opening a link or file. The record lists versions 10.4.3, 10.2.7, 10.0.10 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.15% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Splunk Enterprise to 10.4.3 or 10.2.7 or 10.0.10 or 9.4.15, whichever matches your release line, or a later version.
- Update Splunk to 9.4.15 or 10.0.10 or 10.2.7 or 10.4.3, whichever matches your release line, or a later version.
- Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 10.4 up to, but not including, 10.4.3; 10.2 up to, but not including, 10.2.7; 10.0 up to, but not including, 10.0.10; 9.4 up to, but not including, 9.4.15 | 10.4.3, 10.2.7, 10.0.10, 9.4.15 |
| Splunk | Splunk | 9.4.0 up to, but not including, 9.4.15; 10.0.0 up to, but not including, 10.0.10; 10.2.0 up to, but not including, 10.2.7; 10.4.0 up to, but not including, 10.4.3 | 9.4.15, 10.0.10, 10.2.7, 10.4.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H. Scored by CNA (cisco.com).
Official description
In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15 on Linux, a local user who can run commands as the user account running Splunk Enterprise could cause an affected Linux package upgrade to run attacker-controlled operating-system commands with root privileges. The vulnerability is possible because the Linux package maintainer script trusts existing Splunk Enterprise installation content when it performs upgrade operations with root privileges. The vulnerability requires an affected Linux package upgrade to occur after the local user modifies the installation. The local user should not be able to elevate privileges at will.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Splunk Enterprise
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 9.9 Critical severity
- 8.8 High severity
- 7.2 High severity
Recent Improper Privilege Management vulnerabilities
- 7.1 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.9 Critical severity
Spotted an error? Tell us.