Alert

Logo de Splunk

Alert 2026-175 Critical vulnerabilities in Splunk Enterprise, Enterprise Security and SOAR

Affected product(s): 

ProductAffected versionsFix
Splunk Enterprise10.6.0.5; 10.4.0 to 10.4.4; 10.2.0 to 10.2.8; 10.0.0 to 10.0.11; 9.4.0 to 9.4.1610.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17
Splunk Universal Forwarder10.6.0 to 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; 9.4.0 to 9.4.1610.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17
Splunk Enterprise SecurityBelow 8.7.08.7.0
Splunk App for PCI ComplianceBelow 8.7.08.7.0
Splunk SOARBelow 8.8.08.8.0
Splunk App for StreamBelow 8.1.78.1.7
Splunk AI AssistantBelow 2.0.02.0.0

On the 10.6 branch of Splunk Enterprise, the vendor lists only 10.6.0.5 as affected. Not every Enterprise CVE affects that branch: CVE-2026-76535 does (versions below 10.6.1); CVE-2026-76536, CVE-2026-76538 and CVE-2026-76540 do not list it. Branches that do not appear in the table are not declared safe or affected.

Description

Critical vulnerabilities have been reported in Splunk Enterprise, Splunk Enterprise Security and Splunk SOAR. The vendor made them public on Nov 18, 2026, in its November 2026 advisory batch. The most severe are CVE-2026-131253, CVSS 9.9, critical, and CVE-2026-131287, CVSS 9.6, critical, both in Splunk SOAR; CVE-2026-76536, CVSS 9.4, critical, and CVE-2026-76535, CVSS 9.1, critical, in Splunk Enterprise; and CVE-2026-131202, CVSS 9.1, critical, in Splunk Enterprise Security. This bulletin is classified as CRITICAL.

CVE-2026-76536 is an authentication bypass in the clustering configuration REST API. In 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 on a standalone instance when clustering is turned off. That could expose the configuration, persist attacker-controlled values and disrupt clustering operations. The vendor explains that the product accepts the empty secret as a shared-authentication candidate in that scenario. The 10.6 branch is not listed in the text of this CVE.

CVE-2026-76535 is an authentication bypass in the RapidDiag REST API. In versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12 and 9.4.17, an unauthenticated user could run arbitrary SPL searches through RapidDiag task collection as an authenticated user, and thus read or modify data and configuration available to that user. The vendor explains that the product accepts an empty shared secret when it authenticates those requests.

The same Splunk Enterprise advisory (SVD-2026-1103) fixes 38 product CVEs. Among the high-severity issues are CVE-2026-76538, CVSS 8.8, high, an SPL injection through the REST API via data model acceleration, in versions below 10.4.5, 10.2.9, 10.0.12 and 9.4.16 (the advisory writes 9.4.16, not 9.4.17); and CVE-2026-76540, CVSS 8.8, high, improper authorization through the REST API, in versions below 9.4.17, 10.0.12, 10.2.9 and 10.4.5. In both cases, a user who does not hold the “admin” or “power” roles could cause searches to run with elevated privileges. CVE-2026-76544, CVSS 8.1, high, is also fixed. The vendor does not publish a workaround for these three. The 10.6 branch is not listed in the text of CVE-2026-76538 or CVE-2026-76540.

CVE-2026-131202 is remote code execution through path traversal in the Splunk Enterprise Security REST API. In versions below 8.7.0, a user who holds the ess_admin role could execute arbitrary code on the search head as the account running Splunk Enterprise, by combining lookup file upload and the Configuration Checker function. The vendor explains that the product does not restrict lookup upload file types or keep Configuration Checker module paths within the intended directory. The text of this CVE does not mention the App for PCI Compliance; the role cited is ess_admin. The same advisory (SVD-2026-1106) also calls for updating that app to 8.7.0 and fixes other product flaws, several of them high-severity SPL injections, that require an authenticated user with certain roles or capabilities.

CVE-2026-131253 is remote code execution through the App Wizard. In Splunk SOAR versions below 8.8.0, an authenticated user with Apps edit, Containers edit and Playbooks execute permissions could use the App Wizard to execute arbitrary code as the account that runs Splunk SOAR, and compromise the confidentiality, integrity and availability of the instance. The vendor explains that the App Wizard does not validate user-supplied identifiers before incorporating them into the generated connector code. CVE-2026-131287 is remote code execution through the REST API: a user with Playbooks view, edit, execute and delete permissions could cause cross-repository playbook references to run attacker-controlled code, because SOAR can bind those references to a different source-control repository when a deleted repository name is reused. There is no workaround for these two critical flaws. SVD-2026-1108 covers 59 product CVEs; there are other high-severity flaws that require an authenticated user with specific permissions.

The November batch also includes third-party package advisories for Enterprise, Universal Forwarder, Enterprise Security and SOAR, which are fixed by updating to the same November versions; three CVEs in Splunk App for Stream, the most severe being CVE-2026-131299, CVSS 7.5, high, an unauthenticated XXE injection in the REST API on the management port (8089); and four CVEs in Splunk AI Assistant below 2.0.0, the most severe rated CVSS 8.1, high. On the same day, the vendor published an informative advisory on the Java vulnerability covered in Alert 2026-169, which is not the subject of this bulletin. For prior coverage of the product, on a different flaw, see Alert 2026-105.

As of the date of this bulletin, they are not listed in KEV and no public proof of concept was identified. CVE.org and NVD records for the critical flaws have not yet been published.

Mitigation

Inventory local instances of Splunk Enterprise, Universal Forwarder, Enterprise Security, App for PCI Compliance, SOAR, App for Stream and AI Assistant, including their version.

The fix is to update to the November versions listed in Solution, starting with systems reachable from untrusted networks and with those where accounts hold the cited roles or permissions (ess_admin; apps, containers and playbooks permissions in SOAR).

In the meantime, apply only the workarounds published by the vendor, without combining the pass4SymmKey guidance into a single text:

  • CVE-2026-76536: set a strong, unique pass4SymmKey value of at least 12 characters in the [clustering] stanza of server.conf (the file is at etc/system/local/server.conf under the installation directory), including on standalone instances, and restart Splunk Enterprise.
  • CVE-2026-76535: turn off requests authenticated with an empty shared secret by setting pass4SymmKey to a non-empty value in server.conf if an empty secret is not in use; use the same value on each node that participates in the service and restart.
  • CVE-2026-131192 (7.5, high): set pass4SymmKey to a strong value in the [clustering] stanza of server.conf.
  • CVE-2026-131190 (7.5, high): turn off or remove the RapidDiag app.
  • CVE-2026-131202: turn off or remove the Splunk Enterprise Security app. This is a restrictive measure; updating to 8.7.0 should be the priority.
  • Splunk App for Stream and Splunk AI Assistant: turn off or remove the app if it cannot be updated immediately.
  • For CVE-2026-131253 and CVE-2026-131287 there is no workaround; the fix is to update to 8.8.0.

As an exposure-reduction measure, and not as a vendor workaround for the critical Splunk Enterprise flaws, restrict access to management port 8089 and to the administration interface to trusted networks only. In Splunk App for Stream, the vendor places the XXE injection (CVE-2026-131299) on that port.

After updating or changing pass4SymmKey, restart as indicated in the advisory. Review logs and configurations for unexplained changes, unusual RapidDiag searches or tasks, lookup uploads, App Wizard use, and repository or playbook changes. The patch does not undo a prior compromise. The vendor has not published indicators of compromise.

Solution

The solution is to update to the November 2026 versions published by the vendor, or to a later one:

  • Splunk Enterprise and Splunk Universal Forwarder: 10.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17, according to the branch.
  • Splunk Enterprise Security and Splunk App for PCI Compliance: 8.7.0 or later.
  • Splunk SOAR: 8.8.0 or later.
  • Splunk App for Stream: 8.1.7 or later.
  • Splunk AI Assistant: 2.0.0 or later.

Workarounds do not replace the update. There is no workaround for the two critical Splunk SOAR flaws. Back up the configuration and data before updating.

For information on how to update, visit the following link:

https://advisory.splunk.com/

Additional information: