CVE-2026-76536 PUBLISHED

Authentication Bypass through the Cluster Configuration 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.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration through the cluster configuration Representational State Transfer (REST) API endpoint on a standalone instance. This could expose clustering configuration, persist attacker-controlled clustering settings, and disrupt clustering operations. The vulnerability is possible because Splunk Enterprise accepts the empty clustering shared secret as a shared-authentication candidate on a standalone instance when clustering is turned off.

Metrics

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

Product Status

Vendor Splunk
Product Splunk Enterprise
Versions
  • 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

If you cannot immediately upgrade to a fixed version, set a strong, unique pass4SymmKey value in the [clustering] stanza in the server.conf configuration file, including on standalone instances. The pass4SymmKey value must contain at least 12 characters. The file is at etc/system/local/server.conf under the Splunk Enterprise installation directory. Restart Splunk Enterprise for the change to take effect. 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