CVE-2026-76537 in Splunkinfo

Summary

by MITRE • 11/20/2026

In Splunk Enterprise versions below 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who does not hold a role with either the list_indexer_cluster capability or the edit_indexer_cluster capability could download the cluster manager configuration bundle through the Representational State Transfer (REST) API and access configuration and app files that the cluster manager stages for indexer distribution. The vulnerability is possible because the REST API does not require the list_indexer_cluster or edit_indexer_cluster capability before it sends the configuration bundle. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation. For more information see Cluster endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.6/cluster-endpoints/cluster-endpoint-descriptions) in the Splunk documentation.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

A critical authorization bypass vulnerability exists within Splunk Enterprise versions prior to 10.6.0, specifically affecting releases 10.4.5, 10.2.9, 10.0.12, and 9.4.17. This flaw resides in the implementation of the Representational State Transfer application programming interface used for managing indexer cluster configurations. The vulnerability allows any authenticated user who lacks specific administrative privileges to retrieve sensitive configuration data from the system. Specifically, users without the list_indexer_cluster or edit_indexer_cluster capabilities are able to download the complete cluster manager configuration bundle through standard REST API endpoints that were not properly restricted by role-based access controls.

The technical root cause of this vulnerability is a failure in the server-side authorization logic governing specific cluster management endpoints. The application fails to verify whether the requesting user possesses the necessary permissions before processing the request and transmitting the response data. Consequently, the REST API endpoint responsible for staging configuration files for indexer distribution does not enforce the expected security checks associated with high-privilege roles. This oversight allows an attacker with a low-level or standard user account to bypass intended access restrictions and extract internal system configurations that are meant to be accessible only by cluster administrators.

The operational impact of this vulnerability is significant, as it leads to the exposure of sensitive infrastructure details. By downloading the configuration bundle, an unauthorized actor gains access to app files and configuration settings staged for distribution across indexer nodes within a Splunk deployment. This information can reveal network topology, authentication mechanisms, internal IP addresses, and other architectural details that are critical for maintaining the security posture of the environment. Such exposure facilitates further reconnaissance efforts, potentially enabling more targeted attacks against the Splunk infrastructure or related systems connected to it.

This issue aligns with CWE-269, which describes Improper Privilege Management, as the system fails to enforce appropriate access control levels on a privileged function. Furthermore, from an adversary perspective, this vulnerability supports ATT&CK technique T1505.003, Server Software Component: Web Shell, or more accurately in this context, data exfiltration via legitimate application interfaces similar to T1005 Data from Local System. The ability to retrieve configuration bundles remotely without proper authentication checks represents a direct compromise of the confidentiality integrity principles governing administrative functions within the Splunk platform.

To mitigate this risk, organizations running affected versions must upgrade immediately to Splunk Enterprise version 10.6.0 or later where these access control mechanisms have been corrected. Until an upgrade is feasible, administrators should implement network-level controls such as firewall rules that restrict direct API access from untrusted networks and ensure that all user accounts are assigned the principle of least privilege. Regular auditing of role assignments and monitoring for unusual REST API activity can also help detect potential exploitation attempts while patching efforts are underway.

Responsible

Cisco

Reservation

08/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00221

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!