CVE-2026-76539 in Splunk
Summary
by MITRE • 11/20/2026
In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could use the search jobs Representational State Transfer (REST) API to access indexed events that the srchFilter setting for the role should hide. The same user could also run internal Search Processing Language (SPL) commands and bypass SPL safeguards for risky commands within indexes that the role can search. The vulnerability is possible because Splunk Enterprise does not correctly escape required field values before it includes them in an internally generated search. For more information, see Search endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/9.4/search-endpoints/search-endpoint-descriptions), authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.5-configuration-file-reference/authorize.conf), and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands).
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/20/2026
A critical authorization bypass vulnerability exists in Splunk Enterprise versions prior to 10.4.4, 10.2.9, 10.0.12, and 9.4.16, allowing users with limited privileges to access restricted data and execute prohibited commands. This flaw specifically affects the search jobs Representational State Transfer API endpoint, which is designed to manage ongoing or completed search operations within the platform. Under normal operational conditions, Splunk enforces strict role-based access controls defined in the authorize.conf configuration file. These roles dictate what indexes a user can query and whether they are permitted to execute specific Search Processing Language commands that pose security risks. Users assigned standard roles such as "user" or "readonly," which explicitly lack administrative or power-level privileges, should be prevented from viewing indexed events filtered by srchFilter settings and barred from running internal SPL commands deemed unsafe.
The technical root cause of this vulnerability lies in improper input validation and escaping mechanisms within the search jobs REST API implementation. When a user submits a request through this API to retrieve search results or execute a command, Splunk Enterprise fails to correctly escape required field values before incorporating them into an internally generated search query string. This lack of proper sanitization allows specially crafted inputs to alter the structure or intent of the internal search operation. Consequently, the security filters intended to hide specific indexed events from lower-privileged users are bypassed because the malicious input effectively modifies the scope of the data retrieval process at a level that circumvents standard role-based checks. This mechanism mirrors classic injection flaws where untrusted data is treated as executable code or structural logic within an application context.
The operational impact of this vulnerability is significant, primarily constituting an unauthorized information disclosure and privilege escalation scenario. An attacker with low-level access can extract sensitive indexed events that were explicitly hidden from their role via srchFilter configurations. This exposes potentially confidential business data, personally identifiable information, or security logs to individuals who should not have visibility into them. Furthermore, the ability to run internal Search Processing Language commands bypasses safeguards designed for risky operations. These safeguards are critical for preventing actions such as arbitrary file system access, network connections from within the search head, or execution of external scripts. By circumventing these protections, a low-privileged user can perform actions that typically require administrative oversight, potentially leading to further compromise of the Splunk infrastructure or adjacent systems on the same network segment.
This vulnerability aligns with Common Weakness Enumeration categories such as CWE-269 Improper Privilege Management and CWE-74 Injection in External Control of Search String Parameters. It also maps to MITRE ATT&CK techniques including T1078 Valid Accounts, where an attacker uses legitimate credentials but exploits a flaw to gain higher-level access or data visibility than intended. The exploitation path leverages the REST API interface, which is commonly exposed for automation and integration purposes, making it a high-value target for attackers seeking lateral movement within enterprise environments that rely on Splunk for security information and event management.
Mitigation strategies focus primarily on immediate software updates and configuration hardening. Organizations running affected versions must upgrade to Splunk Enterprise version 10.4.4 or later, which includes patches addressing the input escaping logic in the search jobs REST API. Until an upgrade is feasible, administrators should review access controls within authorize.conf to ensure that sensitive indexes are not accessible via any role that interacts with the search API unless absolutely necessary. Additionally, enabling strict audit logging for all search job submissions can help detect anomalous activity indicative of exploitation attempts. It is also recommended to restrict network-level access to the Splunk management and REST interfaces, ensuring they are only reachable from trusted internal subnets or through secure VPN tunnels, thereby reducing the attack surface available to potential adversaries attempting to leverage this vulnerability.