An attacker with no account on a vulnerable Splunk Enterprise server could run searches on it as a logged-in user, because the software accepts an empty shared secret when it authenticates certain internal requests. That is one of two critical authentication bypasses Splunk fixed this week, in a batch of 80 vulnerabilities across Splunk Enterprise and its Splunk Enterprise Security (ES) app.
Splunk published the fixes on November 18 in two advisories: SVD-2026-1103 for Splunk Enterprise (38 CVEs, highest CVSS 9.4) and SVD-2026-1106 for Enterprise Security and the Splunk App for PCI Compliance (42 CVEs, highest CVSS 9.1). Hong Kong's HKCERT flagged the release in a security bulletin on November 20. Neither advisory says any of the flaws has been exploited, and neither mentions public exploit code.
Two critical bugs hinge on an empty secret
The most severe issue, CVE-2026-76536 (CVSS 9.4), sits in the cluster configuration REST API. According to Splunk, an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration on a standalone instance, which could expose that configuration, persist attacker-controlled clustering settings and disrupt clustering operations. Splunk says the product accepts the empty secret as a valid credential candidate even when clustering is turned off.
CVE-2026-76535 (CVSS 9.1) is in the RapidDiag REST API. Here, Splunk says, an unauthenticated user could run arbitrary Search Processing Language (SPL) searches through RapidDiag task collection as an authenticated user, and read or modify the data and configuration available to that user. The vendor again traces the root cause to Splunk accepting an empty shared secret.
Enterprise Security bug hands code execution to app admins
In the ES app, the critical flaw is CVE-2026-131202 (CVSS 9.1). A user holding the ess_admin role could execute arbitrary code on the search head, as the account running Splunk, by combining lookup file upload with the Configuration Checker feature. Splunk says ES does not restrict lookup upload file types or keep Configuration Checker module paths inside the intended directory. It credits Klevis Luli of Flashpoint with the report. The score's vector marks the bug as requiring high privileges, so an attacker would first need an account with that role.
Most of the remaining fixes are what Splunk labels SPL injection, where, per its descriptions, a user can cause arbitrary SPL commands to run, in several cases with elevated permissions or under another user's identity. Across both advisories Splunk rated 24 issues High, topped by CVE-2026-76538, CVE-2026-76540, CVE-2026-131199 and CVE-2026-131236 at 8.8, plus 51 Medium and 2 Low.
Upgrade to 10.6.1 or ES 8.7.0, or set pass4SymmKey
Fixed Splunk Enterprise versions are 10.6.1, 10.4.5, 10.2.9, 10.0.12 and 9.4.17. The affected releases are 10.6.0.5, 10.4.0 to 10.4.4, 10.2.0 to 10.2.8, 10.0.0 to 10.0.11, and 9.4.0 to 9.4.16. Enterprise Security and the Splunk App for PCI Compliance need version 8.7.0 or later.
Where an immediate upgrade is not possible, Splunk's workaround for both authentication bypasses is a non-empty pass4SymmKey in server.conf. For CVE-2026-76536 it asks for a strong, unique value of at least 12 characters in the clustering stanza, including on standalone instances. For CVE-2026-76535 it asks for the same non-empty value on every node that participates in the service. Both changes need a restart. For the ES code-execution bug, the only workaround Splunk lists is turning off or removing the ES app.
The release follows Splunk's October fixes for flaws that let low-level users run commands. Splunk servers hold an organization's logs and its detection logic, so the two empty-secret bypasses deserve to go first: unlike nearly everything else in this batch, they need no account at all.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.