Splunk says an unauthenticated user could read and change clustering configuration on a standalone instance where clustering is turned off.Splunk published the advisory on November 18, 2026, and rates the flaw Critical at CVSS 3.1 9.4. The issue arises when that standalone instance accepts an empty clustering shared secret as a valid shared-authentication candidate.
What it allows
How Does CVE-2026-76536 Bypass Authentication?
Splunk says a standalone instance with clustering turned off can accept an empty clustering shared secret during shared authentication. An unauthenticated user who can reach the cluster configuration REST API could then read and modify clustering configuration. This is Splunk’s described attack path, not a disclosed request sequence.
Splunk says unauthorized changes could persist attacker-controlled clustering settings and disrupt clustering operations. The impact concerns cluster configuration, rather than RapidDiag searches addressed by a separate CVE in the same advisory. Do not treat every clustered deployment as exposed without checking the stated standalone condition.
What Does the Available Exploitation Evidence Mean?
Splunk describes the vulnerability and its potential impact, but its advisory does not document an exploitation incident. CVE-2026-76536 was absent from CISA’s Known Exploited Vulnerabilities catalog version 2026.11.18. That catalog snapshot does not establish the state of any particular Splunk Enterprise instance.
For local triage, compare current clustering settings with the approved baseline and review unexpected configuration changes. This is our defensive recommendation, not a Splunk detection signature. Place affected servers in a version-based review queue; the Vulnerability Intelligence platform page gives related product context.
Who is affected
Version Check
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 10.4.x | 10.4.0 to before 10.4.5 | 10.4.5 |
| 10.2.x | 10.2.0 to before 10.2.9 | 10.2.9 |
| 10.0.x | 10.0.0 to before 10.0.12 | 10.0.12 |
| 9.4.x | 9.4.0 to before 9.4.17 | 9.4.17 |
For distribution packages and custom builds, check the supplier’s advisory.
Version ranges alone do not establish exposure. Splunk specifies a standalone instance with clustering off and an empty clustering shared secret. The advisory-wide 10.6 row is not named in this CVE description.
Which Splunk Enterprise Versions Are Affected?
Splunk’s CVE-specific description names versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17. The advisory’s product table identifies the affected builds as 10.4.0 through 10.4.4, 10.2.0 through 10.2.8, 10.0.0 through 10.0.11, and 9.4.0 through 9.4.16. The same table includes a 10.6 row for the broader advisory, but this CVE’s description does not name that branch.
The stated exposure also requires a standalone instance with clustering turned off and an empty clustering shared secret accepted for authentication. Inventory standalone servers as well as cluster members when checking the configuration. Use the vulnerability intelligence glossary for the distinction between a published severity score and deployment-specific exposure.
How Should Teams Fix and Verify the Exposure?
For this CVE, Splunk’s branch-specific fixed releases are 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or later. Upgrade the relevant branch, then record the version actually running on each reviewed instance. Retain that evidence in the patch management process.
If an immediate upgrade is impossible, Splunk advises setting a strong, unique pass4SymmKey in the [clustering] stanza of server.conf, including on standalone instances. Splunk requires at least 12 characters and a restart for the change to take effect. Recheck the running version and approved clustering settings after the eventual upgrade.
Timeline
- 2026-11-18
Splunk published SVD-2026-1103 with the CVE-2026-76536 description, affected release branches, and fixed releases.
What to do
-
Find standalone Splunk Enterprise instances
Inventory running versions and identify standalone instances where clustering is turned off. Check the clustering shared-secret configuration on each relevant instance.
-
Upgrade the affected release branch
Upgrade to Splunk Enterprise 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later on the corresponding branch.
-
Verify the running release
After the upgrade and restart, record the release actually running on each reviewed instance. Compare it with Splunk’s fixed release for that branch.
-
Apply Splunk’s temporary mitigation if needed
If upgrade must wait, set a strong, unique clustering pass4SymmKey of at least 12 characters, including on standalone instances, and restart Splunk Enterprise.
-
Review clustering configuration changes
Compare current clustering settings with the approved baseline and investigate unexpected changes. This is our local review advice, not a vendor detection signature.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-76536 in Brandefense Atlas
The Atlas record of CVE-2026-76536: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-76536 require a Splunk login?
Splunk says an unauthenticated user could read and change clustering configuration through the cluster configuration REST API under the stated standalone condition.
Which deployment condition matters most?
Splunk describes a standalone instance with clustering turned off that accepts an empty clustering shared secret. The advisory does not say every cluster member is affected.
Does the advisory list Splunk Enterprise 10.6 for this CVE?
The advisory-wide product table includes 10.6, but the CVE-2026-76536 description names only the 10.4, 10.2, 10.0, and 9.4 release branches.
What is Splunk’s temporary mitigation?
If upgrade must wait, Splunk advises a strong, unique clustering pass4SymmKey of at least 12 characters, including on standalone instances, followed by a restart.