CVE-2026-76345: Remote Code Execution (RCE) through the REST API in Splunk Enterprise

Published Aug 19, 2026
·
Updated

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

1 affected component
Splunk Splunk Enterprise<10.4.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.4.2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.2.6
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.9
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.4.14

Event History

Aug 19, 2026
CVE Published
via MITRE·09:34 PM
Data Sourced
via MITRE·09:34 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203