CVE-2026-76535 in Splunkinfo

Summary

by MITRE • 11/20/2026

In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could run arbitrary Search Processing Language (SPL) searches through RapidDiag task collection as an authenticated user. With this access, the user could read or modify data and configuration available to that authenticated user. The vulnerability is possible because Splunk Enterprise accepts an empty shared secret when it authenticates RapidDiag task-collection requests. For more information see Using RapidDiag (https://help.splunk.com/en/splunk-enterprise/administer/troubleshoot/9.3/contact-splunk-support/using-rapiddiag) in the Splunk documentation.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in Splunk Enterprise versions prior to 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 represents a critical authentication bypass within the RapidDiag diagnostic utility. This component is designed for troubleshooting purposes, allowing support personnel to collect system data remotely. However, the underlying implementation flaw allows an unauthenticated actor to exploit this mechanism by submitting requests with an empty shared secret field. Because the application fails to strictly validate that the shared secret matches a non-empty expected value during the authentication phase of RapidDiag task collection, it erroneously treats these malformed or incomplete credentials as valid. This failure in input validation effectively neutralizes the intended access control mechanisms for this specific endpoint, granting unauthorized entities the ability to impersonate authenticated users who have legitimate access to the system.

From a technical perspective, this flaw constitutes an authentication bypass vulnerability where the security boundary is circumvented due to insufficient verification of credentials. The attacker leverages the RapidDiag interface to execute arbitrary Search Processing Language commands under the context of any valid user account known or discoverable within the Splunk environment. Since SPL allows for complex data queries and modifications, this capability provides a direct pathway to read sensitive information stored in indexes or alter configuration settings that govern system behavior. The exploitation does not require prior authentication credentials, making it particularly dangerous as it can be triggered by remote attackers without any initial foothold inside the network perimeter, provided they have network access to the Splunk management interface.

The operational impact of this vulnerability is severe, encompassing both confidentiality and integrity compromises. An attacker utilizing this flaw can extract sensitive data such as user credentials stored in clear text or hashed forms, internal logs containing proprietary business information, and other confidential metrics collected by the organization. Furthermore, the ability to modify configurations allows for persistent access through backdoor creation, privilege escalation by altering role assignments, or disruption of service integrity by modifying search heads or indexers incorrectly. This aligns with common threat models where attackers seek lateral movement within a network environment after gaining initial access to critical infrastructure components like SIEM platforms.

In terms of industry classification standards, this vulnerability maps directly to CWE-287, which describes Improper Authentication, specifically the failure to verify credentials correctly during an authentication process. Additionally, it relates to CWE-306 regarding Missing Authentication for Critical Function, as the RapidDiag task collection feature should require robust proof of identity before allowing administrative or diagnostic actions. From a tactical perspective within the MITRE ATT&CK framework, this exploit facilitates Initial Access and potentially Lateral Movement by leveraging trusted application features that are misconfigured or poorly secured. It also supports Discovery activities through the execution of arbitrary SPL searches to enumerate system data and configuration details without detection from standard authentication logs if those logs do not distinguish between valid empty-secret requests and legitimate ones.

To mitigate this risk, organizations must immediately upgrade Splunk Enterprise to version 10.6.1 or later, where the validation logic for RapidDiag shared secrets has been corrected to reject empty values. Until patching is complete, administrators should restrict network access to the Splunk management interface using firewalls and ensure that only trusted IP addresses can reach these endpoints. Additionally, reviewing audit logs for unusual SPL execution patterns originating from diagnostic interfaces can help detect ongoing exploitation attempts. It is also advisable to disable unnecessary services like RapidDiag if they are not actively required for support interactions, thereby reducing the attack surface available to potential adversaries seeking to exploit authentication weaknesses in administrative tools.

Responsible

Cisco

Reservation

08/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00367

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!