Splunk has rolled out critical security patches to address high-severity vulnerabilities in both Splunk SOAR and Splunk Enterprise. The most severe vulnerability—CVE-2026-131253—scores a 9.9 out of 10 and enables remote code execution for accounts with specific permissions in SOAR. Meanwhile, a separate authentication bypass issue—CVE-2026-76535—allows unauthenticated users to execute searches in Enterprise under another user’s identity.
What’s at Risk
The SOAR vulnerability CVE-2026-131253 is rooted in the App Wizard component, which helps users create connectors between SOAR and external tools. Users who are signed in and have the ability to edit apps, containers, and run playbooks can exploit this flaw to run code using the SOAR system account’s privileges. This level of access could grant visibility into, or control over, data and configurations normally beyond the user’s reach, making the issue especially dangerous. The advised mitigation is to upgrade to SOAR version 8.8.0 or later. No workaround is provided.
Also included in the same SOAR patch bundle are two other significant flaws: CVE-2026-131287, another remote code execution vulnerability in the REST API rated 9.6, and CVE-2026-131297, a serious single sign-on authentication bypass.
On the Enterprise side, CVE-2026-76535 allows unauthenticated attackers to access the RapidDiag REST API component, which is meant for gathering diagnostic data. The flaw arises from improper username validation, enabling attackers to run Search Processing Language (SPL) queries using another user’s identity. While this does not permit code execution on the underlying operating system, it can expose data or settings depending on the impersonated user’s permissions.
Upgrade Paths & Recommendations
Admins running SOAR older than 8.8.0 should apply the update immediately. For Enterprise users, patched versions include 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17—depending on the branch in use. Note that these fixes are product-specific: updating Splunk Enterprise does not protect SOAR, and vice versa. The SOAR 8.7.0 update from October lacks the November fixes.
After updating, operators are urged to verify their instance versions and test critical functionality like searches, connectors, and playbooks. If there’s suspicion that an attack or misuse occurred before the patches were applied, preserving logs and reviewing any odd behavior—such as unauthorized searches or unexpected app/container alterations—is critical, since the patches themselves can’t detect prior exploitation.
SOAR is Splunk’s Security Orchestration, Automation, and Response platform—used to streamline and automate incident response workflows. Enterprise is the broader search, monitoring, and analytics suite central to Splunk’s threat detection and operational intelligence offerings. These vulnerabilities hit both in so far as they affect workflow integrity and data access.
This update follows Splunk’s October release, which addressed 24 vulnerabilities across both SOAR and Enterprise, including four critical ones. This latest batch underscores that the platform remains under significant pressure from exploit attempts targeting high-risk flaws.
What this means: organizations using Splunk, especially those running both SOAR and Enterprise, are urged to treat this as an emergency patch cycle. The 9.9-rated vulnerability isn’t just technical — it represents a foothold that could unlock cascading risks. Watch for upcoming threat intelligence on whether these flaws have been exploited in the wild, and make sure your SOCs are armed with version details, penetration assessment, and audits of past activity to detect any signs of breach.