Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Splunk SOAR and Enterprise November Fixes: Patch Now

Splunk November 2026 fixes cover SOAR 8.8.0 and five Enterprise branches. Compare fixed versions, critical CVE conditions, and patch priorities.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
19 November 2026
Reading time
3 min read
Two software stacks aligned with a security update pathway

Splunk November 2026 fixes are available for SOAR and Enterprise deployments. Splunk published both advisories on November 18: upgrade SOAR to 8.8.0 or later, and move Enterprise installations to the fixed release for their branch. Start by checking the running version and the permissions or configuration that make each critical flaw reachable.

The SOAR advisory rates its highest issue Critical at CVSS 3.1 9.9. The Enterprise advisory reaches Critical at CVSS 3.1 9.4. These scores describe different flaws and do not establish that either product is under active attack.

Splunk November 2026 Fixes by Product and Branch

Splunk’s product-status tables provide the following affected and fixed versions. The Enterprise 10.6 row specifically lists 10.6.0.5 as affected; do not turn that entry into a claim about every 10.6 build.

Product or branch Version Splunk lists as affected Fixed release
Splunk SOAR 8.8 Below 8.8.0 8.8.0 or later
Splunk Enterprise 10.6 10.6.0.5 10.6.1
Splunk Enterprise 10.4 10.4.0 to 10.4.4 10.4.5
Splunk Enterprise 10.2 10.2.0 to 10.2.8 10.2.9
Splunk Enterprise 10.0 10.0.0 to 10.0.11 10.0.12
Splunk Enterprise 9.4 9.4.0 to 9.4.16 9.4.17

Record the installed build for each instance before scheduling a change. The vulnerability intelligence platform can help organize prioritization across products, while Splunk’s advisory remains the source for the required fixed version.

Which Critical Paths Deserve the First Change Window?

In SOAR, CVE-2026-131253 is a code injection flaw in App Wizard. Splunk says an authenticated user needs Apps edit, Containers edit, and Playbooks execute permissions to run code as the SOAR service account. Splunk scores it 9.9 under CVSS 3.1.

A second SOAR issue, CVE-2026-131287, scores 9.6 under CVSS 3.1 and has a different prerequisite. Splunk describes a user with Playbooks view, edit, execute, and delete permissions who could make an existing cross-repository reference run attacker-controlled playbook code. Review both permission sets when ranking SOAR installations.

In Enterprise, CVE-2026-76535 scores 9.1 under CVSS 3.1. Splunk says an unauthenticated user could run searches with an authenticated user’s access when RapidDiag task collection accepts an empty shared secret. The resulting searches could read or change data and configuration available to that user.

CVE-2026-76536 scores 9.4 under CVSS 3.1 and concerns a standalone instance with clustering turned off. Splunk says an unauthenticated user could read or change clustering configuration when an empty clustering secret is accepted. Its description names Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17; it does not name the 10.6 branch for this CVE.

What Should Splunk Owners Do Now?

Use the fixed-version table to create separate SOAR and Enterprise change tickets. For SOAR, review who has the named app, container, and playbook permissions. For Enterprise, check whether RapidDiag and standalone clustering configurations match the conditions in Splunk’s two authentication-bypass descriptions.

Splunk patch sequence
  • InventoryRecord the running SOAR or Enterprise build and the deployment owner.
  • PrioritizeCheck SOAR role permissions and Enterprise shared-secret and clustering conditions.
  • UpgradeApply Splunk’s fixed release for each affected branch.
  • VerifyConfirm the running build after restart and review the affected access paths.

Splunk gives a specific interim measure for CVE-2026-76535: set a nonempty pass4SymmKey consistently on participating nodes, then restart Enterprise. Follow the vendor’s configuration guidance before changing this shared secret. The advisory’s fix is still the applicable patched release.

Brandefense Blackhole counted 323 dark-chat posts mentioning Splunk from August 21 through November 19, 2026. That count measures broad discussion, not posts verified as about these CVEs or distinct incidents. It cannot establish exploitation of the November fixes.

Track the completed upgrades in a patch management process. For context, our earlier Splunk Enterprise RCE coverage concerns a separate 2022 issue. Splunk’s November advisories list CVSS 3.1 scores but do not provide CVSS 4.0 scores.

Frequently Asked Questions

Which Splunk SOAR version fixes the November vulnerabilities?

Splunk identifies SOAR 8.8.0 or later as the fix. Check the running version after the upgrade.

Does CVE-2026-76536 affect Enterprise 10.6?

Splunk's CVE-specific description names the 10.4, 10.2, 10.0, and 9.4 branches. The broader advisory lists 10.6.1 for other Enterprise fixes.

Is the SOAR App Wizard flaw unauthenticated?

No. Splunk says CVE-2026-131253 requires an authenticated user with Apps edit, Containers edit, and Playbooks execute permissions.

Sources

  1. Splunk SOAR Security Vulnerabilities, November 2026
  2. Splunk Enterprise Security Vulnerabilities, November 2026
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →