CVE-2026-76536 shows that authentication defects and network exposure must be assessed together. An affected standalone Splunk Enterprise instance with clustering disabled and an empty clustering shared secret can accept an unauthenticated caller through the cluster configuration REST API. That caller may read or modify clustering configuration. Splunk rates the issue 9.4 under CVSS 3.1.
Vulnerability overview
Splunk advisory SVD-2026-1103 published the issue on November 18, 2026. It affects Splunk Enterprise and is classified as CWE-287. The vulnerable endpoint is the cluster configuration REST API. The vendor describes accepted use of an empty clustering shared secret when clustering is disabled.
Network controls do not fix the application flaw, but they change who can reach it. A vulnerable service accessible only from a tightly controlled administrative path has a smaller immediate attack surface than the same service exposed to a general user or partner network.
Mechanism and exploitation conditions
The attacker needs to reach the API. The target must run an affected release, be standalone with clustering off and have an empty clustering shared secret. The empty value is then accepted as a shared-authentication candidate.
The CVSS vector notes network access, low complexity, no privileges and no user interaction. Those characteristics make reachability reduction valuable during the period before patching. The advisory does not provide exploit code, so validation should rely on vendor facts and controlled internal testing.
Impact
Configuration reads can expose deployment details. Configuration writes can persist unauthorized settings and disrupt future clustering operations. Integrity and availability impact are high. Confidentiality impact is low, but architecture information may still support follow-on activity.
The persistence aspect affects incident response. A blocked network path may stop new requests while leaving an earlier change in place. Responders must inspect configuration state as well as packet-level controls.
Affected products and scope
The CVE description names Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12 and 9.4.17. The advisory lists fixed releases for each product-status row.
Map the management plane separately from data ingestion and user access. Identify which networks can reach the cluster configuration API, which identities and services use it and whether those paths are necessary. Include standalone systems that are not current cluster members because the vulnerable condition applies specifically when clustering is off.
Exposure context
The stored ZoomEye search app="Splunk" returned 47,748 matches. The CVE filter vul.cve="CVE-2026-76536" returned 0. Exposure is 47,748 product fingerprints and does not prove a vulnerable configuration.
The count illustrates why product-based inventory is insufficient. ZoomEye can find Splunk fingerprints, but local evidence must determine clustering state, secret state and access paths. No reviewed source confirms exploitation in the wild.
Remediation and mitigations
Patch to a fixed release first. Where a delay is unavoidable, set a strong, unique pass4SymmKey with at least 12 characters in the [clustering] stanza of server.conf, including on standalone instances. Restart Splunk Enterprise after the change.
Restrict management access to trusted networks and administration paths. Review firewall, cloud security group and load-balancer rules that may make the endpoint reachable from unexpected segments. Do not assume that an internal source is trusted. A compromised workstation or integration credential can originate inside the perimeter.
Monitor configuration changes and API activity. Investigate requests that do not match an approved change, especially when the source is unusual or the request succeeds without an expected authenticated identity. Revalidate the configuration after containment.
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 active exploitation.