CVE-2026-76535

Authentication Bypass through the RapidDiag REST API in Splunk Enterprise

Published Nov 19, 2026 CVSS 3.1 · 9.1 Critical EPSS n/a KEV · Not listed
Description
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.

Remediation

Vendor Solution

Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.


Vendor Workaround

Turn off requests authenticated with an empty shared secret by setting `pass4SymmKey = <non-empty value>` in the `server.conf` configuration file if you do not use an empty shared secret. Use the same value on each node that participates in the service and restart Splunk Enterprise after the change. For more information see [Secure Splunk Enterprise services with pass4SymmKey](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/secure-distributed-and-clustered-splunk-environments/secure-splunk-enterprise-services-with-pass4symmkey) in the Splunk documentation.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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.
Title Authentication Bypass through the RapidDiag REST API in Splunk Enterprise
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
cisco
Published
Updated
Nov 19, 2026, 7:55 PM
Reserved
Aug 19, 2026, 12:02 PM
Status
Received
Published
Nov 19, 2026, 8:17 PM
Modified
Nov 19, 2026, 8:17 PM