CVE-2026-76266: Local Privilege Escalation through Linux Package Upgrades in Splunk Enterprise
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.4.3 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.7 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.10 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.15
Event History
Frequently Asked Questions
Who is realistically exposed to this issue?
Linux deployments of Splunk Enterprise below 10.4.3, 10.2.7, 10.0.10, or 9.4.15 are exposed if a local user can run commands as the account that runs Splunk Enterprise. The issue is tied specifically to Linux package upgrade operations.
What must an attacker do to obtain root-level command execution?
The attacker must first be able to modify the existing Splunk Enterprise installation while running as the Splunk Enterprise service account. An affected Linux package upgrade must then be performed, causing the package maintainer script to execute attacker-controlled operating-system commands as root.
Can the local user elevate privileges immediately after modifying the installation?
No. The described escalation depends on a subsequent affected Linux package upgrade, so the local user should not be able to elevate privileges at will.
What versions remediate the issue?
Upgrade Splunk Enterprise to 10.4.3, 10.2.7, 10.0.10, or 9.4.15, as applicable to the deployed release line.