CVE-2026-76535 PUBLISHED

Authentication Bypass through the RapidDiag REST API in Splunk Enterprise

Assigner: cisco
Reserved: 19.08.2026 Published: 19.11.2026 Updated: 20.11.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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS Score: 9.1

Product Status

Vendor Splunk
Product Splunk Enterprise
Versions
  • affected from 10.6 to 10.6.1 (excl.)
  • affected from 10.4 to 10.4.5 (excl.)
  • affected from 10.2 to 10.2.9 (excl.)
  • affected from 10.0 to 10.0.12 (excl.)
  • affected from 9.4 to 9.4.17 (excl.)

Workarounds

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 in the Splunk documentation.

Solutions

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

References

Problem Types

  • When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct. cwe