{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-76536","assignerOrgId":"d1c1063e-7a18-46af-9102-31f8928bc633","state":"PUBLISHED","assignerShortName":"cisco","dateReserved":"2026-08-19T12:02:03.644Z","datePublished":"2026-11-19T19:55:23.388Z","dateUpdated":"2026-11-19T19:55:23.388Z"},"containers":{"cna":{"affected":[{"product":"Splunk Enterprise","vendor":"Splunk","versions":[{"version":"10.4","status":"affected","versionType":"custom","lessThan":"10.4.5"},{"version":"10.2","status":"affected","versionType":"custom","lessThan":"10.2.9"},{"version":"10.0","status":"affected","versionType":"custom","lessThan":"10.0.12"},{"version":"9.4","status":"affected","versionType":"custom","lessThan":"9.4.17"}],"modules":["REST API"]}],"descriptions":[{"lang":"en","value":"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.\nThe 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."}],"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1103"}],"title":"Authentication Bypass through the Cluster Configuration REST API in Splunk Enterprise","datePublic":"2026-11-18T00:00:00.000Z","problemTypes":[{"descriptions":[{"lang":"en","type":"cwe","cweId":"CWE-287","description":"When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct."}]}],"source":{"advisory":"SVD-2026-1103","discovery":""},"providerMetadata":{"orgId":"d1c1063e-7a18-46af-9102-31f8928bc633","shortName":"cisco","dateUpdated":"2026-11-19T19:55:23.388Z"},"metrics":[{"cvssV3_1":{"vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H","version":"3.1","baseScore":9.4,"baseSeverity":"CRITICAL"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"solutions":[{"lang":"en","value":"Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher."}],"workarounds":[{"lang":"en","value":"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.\nFor more information see [Secure Splunk Enterprise services with pass4SymmKey](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/secure-distributed-and-clustered-splunk-environments/secure-splunk-enterprise-services-with-pass4symmkey) in the Splunk documentation."}]}}}