CVE-2026-76345: Remote Code Execution (RCE) through the REST API in Splunk Enterprise
In Splunk Enterprise versions below 10.4.2, a user with a high-privilege Splunk role that can manage search head clustering could use the search head cluster member bundle Representational State Transfer (REST) API to write files to locations that the user account running Splunk Enterprise can write to, which could allow for remote code execution. Successful exploitation could result in access to all relevant data and could affect the integrity and availability of the Splunk deployment. The vulnerability does not affect Splunk Enterprise versions below 10.4. The vulnerability is possible because the search head cluster member bundle REST API does not enforce the expected authorization boundary and does not validate bundle paths before accepting bundle content. For more information see Using the REST API reference (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/10.2/introduction/using-the-rest-api-reference), About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access), and About distributed search (https://help.splunk.com/en/splunk-enterprise/administer/distributed-search/9.4/overview-of-distributed-search/about-distributed-search) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.4.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.2.6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 9.4.14
Event History
Frequently Asked Questions
Which deployments are affected?
The issue affects Splunk Enterprise versions 10.4 through versions below 10.4.2. Splunk Enterprise versions below 10.4 are not affected.
What level of access does an attacker need?
An attacker must already have a high-privilege Splunk role with permission to manage search head clustering. They would use the search head cluster member bundle REST API to write content to filesystem locations writable by the account running Splunk Enterprise.
What is the likely impact if exploitation succeeds?
Successful exploitation could allow remote code execution in the context of the account running Splunk Enterprise. This could expose relevant data and affect the integrity and availability of the Splunk deployment.
How can administrators determine whether they are exposed?
Check whether the deployment runs a version from 10.4 up to, but not including, 10.4.2, and whether any high-privilege roles can manage search head clustering. Exposure depends on access to the search head cluster member bundle REST API and the ability to write bundle content to paths writable by the Splunk Enterprise service account.