CVE-2026-76540 in Splunkinfo

Summary

by MITRE • 11/20/2026

In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user access or modify data and disrupt the Splunk Enterprise instance. The vulnerability occurs because Splunk Enterprise does not enforce the required role-based authorization when it processes metric alert configuration through the REST API. Splunk Enterprise schedules the resulting search with elevated authorization and runs attacker-controlled search processing with that authorization. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/20/2026

A critical privilege escalation vulnerability exists within Splunk Enterprise versions prior to 9.4.17, 10.0.12, 10.2.9, and 10.4.5, allowing unauthorized users to execute searches with elevated privileges through the Representational State Transfer API. This flaw specifically impacts metric alert configurations, where a user lacking administrative or power roles can manipulate system behavior by submitting crafted requests that bypass standard role-based access controls. The vulnerability stems from an insufficient authorization check during the processing of these specific configuration endpoints, leading to a scenario where the application schedules and executes search operations under higher privilege levels than intended for the initiating user account.

The technical root cause lies in the failure of Splunk Enterprise to enforce strict role-based authorization when handling metric alert setup via its REST API interface. When an unprivileged user submits a request to configure such an alert, the system incorrectly associates the resulting scheduled search with elevated permissions rather than restricting it to the caller's limited scope. Consequently, any search logic defined within this configuration is executed using these unauthorized high-level credentials. This mechanism effectively allows attackers to run arbitrary commands or queries that they would otherwise be prohibited from accessing, creating a significant breach in the principle of least privilege that underpins secure system architecture.

The operational impact of this vulnerability is severe, as it grants low-privilege users the ability to access sensitive data and modify critical configurations across the Splunk Enterprise instance. Attackers can leverage this capability to exfiltrate confidential information stored within indexed logs or dashboards, potentially leading to significant data breaches depending on the sensitivity of the monitored environment. Furthermore, by executing arbitrary search processing with elevated rights, adversaries can disrupt normal operations, degrade system performance through resource exhaustion, or even compromise other components connected to the Splunk platform if those systems trust the integrity of alerts generated within it.

This vulnerability aligns with CWE-269, which describes Improper Privilege Management, as well as aspects of CWE-862 regarding Missing Authorization checks in critical code paths. In terms of offensive security frameworks, this behavior corresponds to MITRE ATT&CK technique T1078, Valid Accounts, where an attacker uses legitimate credentials with insufficient privileges to gain higher-level access through application logic flaws rather than credential theft. The exploitation vector is remote via the REST API, making it accessible to any authenticated user who can reach the service interface without requiring additional network proximity or physical access.

To mitigate this risk, organizations must immediately upgrade Splunk Enterprise to version 9.4.17, 10.0.12, 10.2.9, or later, as these releases contain patches that enforce proper role-based authorization for metric alert configurations via the REST API. Until patching is complete, administrators should restrict access to the Splunk management interface using network segmentation and firewall rules to limit exposure to trusted internal networks only. Additionally, implementing strict input validation on all API endpoints and auditing user permissions regularly can help detect anomalous activity indicative of exploitation attempts. Regular review of scheduled searches and alert configurations against current role assignments is also recommended to ensure no residual misconfigurations exist that could be leveraged by malicious actors.

Responsible

Cisco

Reservation

08/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00302

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!