Splunk fixes CVE-2026-76536, a Critical authentication bypass
Splunk published fixes for CVE-2026-76536, a Critical 9.4 authentication bypass that an unauthenticated user could reach with an empty clustering shared secret on a standalone Splunk Enterprise instance.
Splunk has published fixes for CVE-2026-76536, an authentication bypass through the Cluster Configuration REST (representational state transfer) API in Splunk Enterprise. The vulnerability carries a CVSSv3.1 (Common Vulnerability Scoring System version 3.1) score of 9.4, rated Critical.
What is affected
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 are affected by CVE-2026-76536. The state the advisory describes is a standalone instance with clustering turned off, where Splunk Enterprise accepts an empty clustering shared secret as a shared-authentication candidate.
Why it matters
It is classified as CWE-287 (Common Weakness Enumeration: Improper Authentication), the category for products that do not correctly verify a claim of identity. The consequence is direct: an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration through the cluster configuration REST API endpoint on a standalone instance.
What to do
Splunk Enterprise 10.6.1 fixes CVE-2026-76536. Fixed releases are also published as 10.4.5, 10.2.9, 10.0.12, and 9.4.17. If upgrading is not possible, Splunk advises setting a strong, unique pass4SymmKey of at least 12 characters in the [clustering] stanza of server.conf.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .