Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Screenshot of the Splunk Security Advisories page listing the November 2026 advisories for Splunk AI Assistant, App for Stream, SOAR, Enterprise Security, Universal Forwarder and Enterprise, with severity ratings.
Image: Splunk (fair use). The Splunk Security Advisories index, showing the advisories published Nov. 18, 2026.

Tools

Splunk Fixes 139 Flaws in the SIEM and SOAR Tools Security Teams Run On, Including Empty-Secret Bypasses That Let Outsiders Run Searches and Analyst-Role Bugs That Turn Detection Content Into a Path to Higher Privileges

The November release covers Splunk Enterprise, Enterprise Security and SOAR. Two Enterprise flaws accept an empty shared secret from unauthenticated users, and several Enterprise Security bugs let an analyst plant search logic that scheduled jobs later run with elevated permissions.

James Whitford, ToolsAustin6 min read

AUSTIN - Splunk on Wednesday published fixes for 139 vulnerabilities in the three products at the center of many security operations centers, its Enterprise platform, the Enterprise Security SIEM app and the SOAR automation product, including two flaws that let an unauthenticated user act on a Splunk Enterprise server because it accepts an empty shared secret.

The release, published as separate advisories on the company's security portal, covers 38 vulnerabilities in Splunk Enterprise, 42 in Enterprise Security and 59 in SOAR. Five are rated critical. Splunk also shipped fixes for three flaws in its App for Stream and four in its AI Assistant, and updated third-party packages bundled with Enterprise, Enterprise Security, SOAR and the Universal Forwarder. The advisories do not say that any of the flaws have been exploited.

For security teams the release lands differently than a typical vendor patch day. The affected systems hold detection logic, stored credentials for the tools they query, and the playbooks that can quarantine hosts and disable accounts. A large share of the bugs are not about outsiders breaking in but about what a logged-in user with a modest role can make the platform do on their behalf.

Two ways in with an empty secret

The most serious Splunk Enterprise flaw, CVE-2026-76536, scored 9.4, affects standalone instances with clustering turned off. Splunk said such an instance accepts an empty clustering shared secret as a valid credential, letting an unauthenticated user read and modify clustering configuration through the cluster configuration REST API, persist attacker-controlled settings and disrupt clustering operations.

The second, CVE-2026-76535, scored 9.1, goes further. Because Splunk Enterprise accepts an empty shared secret when it authenticates RapidDiag task-collection requests, an unauthenticated user could run arbitrary Search Processing Language searches as an authenticated user, with whatever read and write access that user has to data and configuration. A related high-severity bug, CVE-2026-131190, lets unauthenticated users reach RapidDiag process metadata and log file inventories because certain endpoints accept a factory-default shared key.

Screenshot of Splunk advisory SVD-2026-1103 for Splunk Enterprise, showing fixed versions 10.6.1, 10.4.5, 10.2.9, 10.0.12 and 9.4.17 and a vulnerability table led by two critical authentication bypasses.
Image: Splunk (fair use).Splunk advisory SVD-2026-1103, Security Vulnerabilities in Splunk Enterprise, Nov. 18, 2026.

Fixed Enterprise releases are 10.6.1, 10.4.5, 10.2.9, 10.0.12 and 9.4.17. For administrators who cannot upgrade right away, Splunk's workaround for both critical flaws is the same setting: a non-empty pass4SymmKey in server.conf. For the clustering bug, it said the value belongs in the [clustering] stanza even on standalone instances and must be at least 12 characters, followed by a restart. For the RapidDiag bug, the same value must be used on every node that participates in the service. Removing the RapidDiag app closes the factory-key issue.

Thirteen other Enterprise flaws are rated high. Most are SPL injection bugs reachable through the REST API, metric alert filters, saved search dispatch, dashboards and data model acceleration.

When the analyst role becomes the attack path

Enterprise Security 8.7.0, which Splunk names as the fix along with the matching Splunk App for PCI Compliance release, addresses 42 issues. The only critical one, CVE-2026-131202, scored 9.1, lets a user with the ess_admin role run arbitrary code on the search head as the account that runs Splunk, by combining lookup file uploads with the Configuration Checker. Splunk said the app neither restricts lookup file types nor keeps Configuration Checker module paths inside the intended directory. It credited Klevis Luli of Flashpoint, and its only workaround is to turn off or remove Enterprise Security.

Screenshot of Splunk advisory SVD-2026-1106 for Splunk Enterprise Security, showing a highest CVSS score of 9.1, the fixed version 8.7.0 and CVE-2026-131202, remote code execution through REST API path traversal.
Image: Splunk (fair use).Splunk advisory SVD-2026-1106, Security Vulnerabilities in Splunk Enterprise Security, Nov. 18, 2026.

The high-severity bugs are more uncomfortable for SOC managers because they start from ess_analyst, the everyday role analysts use to work findings. Under CVE-2026-131203, an analyst could edit the search macro tied to risk exclusions, which the app's own metadata grants that role write access to. Scheduled Risk data model acceleration searches would later run the planted SPL with elevated permissions, which Splunk said could expose stored credentials and modify indexes or lookup data. Under CVE-2026-131200, an analyst could create a saved search that threat intelligence lookup generation later runs with elevated permissions. Under CVE-2026-131210, a finding exclusion rule could reference an attacker-controlled lookup definition that the UEBA content app later drops unquoted into a search. Splunk lists no workaround for those three.

In practice, that means a stolen or misused analyst account is worth more than its role suggests until Enterprise Security is upgraded. Teams that cannot move to 8.7.0 quickly can at least review who holds ess_analyst and ess_admin and look for recent edits to risk exclusion macros, saved searches and finding exclusion rules.

SOAR: playbook code and identity provider mix-ups

SOAR 8.8.0 fixes 59 flaws, 25 of them high and two critical, and Splunk lists no workarounds for either critical bug. CVE-2026-131253, scored 9.9, lets an authenticated user whose role can edit apps and containers and execute playbooks use the App Wizard to run arbitrary code as the SOAR service account, because the wizard does not validate identifiers it writes into generated connector code. CVE-2026-131287, scored 9.6, arises when a deleted source control repository name is reused: SOAR can bind existing cross-repository playbook references to the new repository and run attacker-controlled playbook code.

Screenshot of Splunk advisory SVD-2026-1108 for Splunk SOAR, showing a highest CVSS score of 9.9, the fixed version 8.8.0 and CVE-2026-131253, remote code execution through the App Wizard.
Image: Splunk (fair use).Splunk advisory SVD-2026-1108, Security Vulnerabilities in Splunk SOAR, Nov. 18, 2026.

A third SOAR bug, CVE-2026-131297, affects deployments with more than one external identity provider. Splunk said SOAR authenticated accounts by username without checking which provider owned them, so an operator of one configured identity provider could sign in as an existing user tied to another, and take control of the deployment if that account held the Administrator role.

Separately, Splunk said in a Java4Shell advisory published the same day that Splunk Cloud Platform, Splunk Enterprise, the Universal Forwarder and SOAR are not affected by Java4Shell, CVE-2026-114938, the heap overflow in the Java runtime, while it investigates the rest of its product line. Cisco, Splunk's parent company, lists the Splunk AppDynamics On-Premises Virtual Appliance as affected.

About the Author

James Whitford

James Whitford covers SOC tooling, SIEM, SOAR, and detection platforms for SOCtember from Austin.

Related stories

Tools desk