CVE-2026-76289: Denial of Service (DoS) through the REST API in Splunk Enterprise

Published Oct 21, 2026
·
Updated

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could make the Splunk Enterprise instance unavailable to other users by sending a request to the Representational State Transfer (REST) API endpoint for lookup table files. The affected instance requires a restart to restore service. The vulnerability is possible because the endpoint does not limit resource use when it processes response field selections. For more information see Endpoints reference list (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/10.4/introduction/endpoints-reference-list) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

Affected Software

1 affected component
Splunk Splunk Enterprise<10.4.4, <10.2.8, <10.0.11, <9.4.16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.4.4
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.8
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.11
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.16

Event History

Oct 21, 2026
CVE Published
via MITRE·10:51 PM
Data Sourced
via MITRE·10:51 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Splunk Enterprise versions earlier than 10.4.4, 10.2.8, 10.0.11, and 9.4.16 are affected.

2

What access does an attacker need?

An attacker needs access as a Splunk user that does not have the admin or power role. Exploitation is performed by sending a request to the REST API endpoint for lookup table files.

3

What is the operational impact of successful exploitation?

The affected Splunk Enterprise instance can become unavailable to other users. A restart is required to restore service.

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