Skip to content

CVE-2026-76536 Exploitability: What CVSS 9.4 Does and Does Not Tell You

Technical analysis of CVE-2026-76536 Exploitability: What CVSS 9.4 Does and Does Not Tell You.

ivanova
Nov 22, 20263 min read

VE-2026-76536 has a critical vendor score, but exploitability in a specific environment depends on configuration. Splunk Enterprise can accept an empty clustering shared secret on a standalone instance when clustering is disabled. A remote unauthenticated caller can then read or modify clustering configuration through the cluster configuration REST API. The CVSS 3.1 score is 9.4.

Vulnerability overview

Splunk advisory SVD-2026-1103 published the issue on November 18, 2026 and classified it as CWE-287. The affected product is Splunk Enterprise. The relevant deployment is a standalone instance with clustering off and an empty clustering shared secret.

The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H. It describes a network attack with low complexity, no required privileges, no user interaction, low confidentiality impact, high integrity impact and high availability impact.

Mechanism and exploitation conditions

The cluster configuration REST API uses a shared secret for authentication. In the affected state, an empty clustering secret can be accepted as a candidate instead of being rejected. The attacker can then perform configuration operations without a valid secret.

The vulnerable condition is narrower than the product scope alone. A Splunk Enterprise deployment with a non-empty clustering secret does not match the advisory description. The endpoint must also be reachable from the attacker's location. These conditions make local validation necessary.

The reviewed sources do not include a proof of concept or a request-level exploit recipe. The absence of public exploit code does not reduce the need to patch, but it limits claims about how easily a particular deployment can be attacked.

Impact

An unauthenticated caller can read clustering configuration and persist changes. The integrity impact is high because the attacker controls stored settings. Availability impact is high because those changes can disrupt clustering operations or later deployment work.

Confidentiality impact is rated low. Configuration data can still be useful to an attacker who wants to understand the deployment before making other moves. Responders should review surrounding administrative activity as well as the cluster configuration itself.

Affected products and scope

The CVE text names Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12 and 9.4.17. The advisory's product-status table provides fixed versions for the affected release families.

Scope checks should answer four questions. Is the build affected? Is clustering off? Is the clustering shared secret empty? Can an untrusted source reach the API? A CVSS score alone cannot answer any of them.

Exposure context

The stored ZoomEye search app="Splunk" returned 47,748 matches on November 22, 2026 UTC. The filter vul.cve="CVE-2026-76536" returned 0. Exposure is 47,748 product-fingerprint matches.

That number does not mean 47,748 vulnerable systems. It means ZoomEye identified Splunk fingerprints. The CVE-specific filter returned a successful zero, so the result is evidence of no indexed CVE-tagged matches at that time, not a query failure. Neither observation proves exploitation.

Remediation and mitigations

Upgrade to a fixed release. If an upgrade is delayed, set a strong and unique pass4SymmKey with at least 12 characters in the [clustering] stanza of server.conf, including on standalone systems. Restart Splunk Enterprise so the setting takes effect.

Validate the build, effective configuration and network reachability after the change. Review API and configuration activity for unauthorized updates and preserve evidence before correcting any unexpected setting. Coordinate secrets with future cluster members as part of the remediation plan.

The appropriate priority is urgent for systems that match the configuration condition. The appropriate claim is narrower: the issue is remotely reachable and critical under the vendor score, and exploitation in a specific estate depends on the local configuration and access path.

References

  • Splunk SVD-2026-1103: https://advisory.splunk.com/advisories/SVD-2026-1103
  • GitHub advisory GHSA-c7vg-cjh6-hffq: https://github.com/advisories/GHSA-c7vg-cjh6-hffq
  • NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-76536

The reviewed sources do not confirm exploitation in the wild.

Did you enjoy this article?

Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.

Across the AtmosphereDiscussions