Skip to content

CVE-2026-131253

Splunk SOAR App Wizard remote code execution for authenticated users (CVE-2026-131253)

Critical 9.9 Vendor: Cisco Published

Splunk SOAR before 8.8.0 lets an authenticated user with Apps edit, Containers edit and Playbooks execute permissions run arbitrary code as the account that runs the SOAR instance. Upgrade to 8.8.0.

What happened

An authenticated user who holds a role with three permissions — Apps edit, Containers edit, and Playbooks execute — can use the App Wizard in Splunk SOAR to execute arbitrary code as the account that runs the SOAR instance. The App Wizard does not validate user-supplied identifiers before incorporating them into generated connector code. This is a network-based, low-privilege, no-user-interaction issue: an attacker with those permissions can compromise the confidentiality, integrity and availability of the SOAR instance, and the scope can change beyond the vulnerable component. The CVSS v3.1 score is 9.9, critical.

The CVE record does not report exploitation and Splunk has not said the flaw was publicly disclosed before the advisory.

Who is affected

Splunk SOAR versions before 8.8.0 are affected. Deployments are exposed where users can be assigned the Apps edit, Containers edit and Playbooks execute permissions. Check the version of any Splunk SOAR instance you operate and review the roles and accounts holding those permissions.

What to do now

  1. Identify Splunk SOAR instances running versions before 8.8.0.
  2. Upgrade to Splunk SOAR 8.8.0. This is the fixed version listed for CVE-2026-131253.
  3. Review accounts and roles with Apps edit, Containers edit and Playbooks execute permissions, and remove the combination from users who do not need it.
  4. Splunk has not listed a workaround, so treat the upgrade as the primary remediation. Until it is complete, restrict access to the SOAR management interface to trusted administrators and monitor for unusual App Wizard activity.

How to detect it

Review Splunk SOAR audit history for App Wizard activity by accounts that hold Apps edit, Containers edit and Playbooks execute permissions. Because the flaw involves user-supplied identifiers, examine newly generated or changed connector code closely. Monitor the account that runs Splunk SOAR for unexpected process execution or outbound connections.

Beyond the patch

A SOAR platform operates with access to the tools and systems it orchestrates, so code execution under its service account can have a wide blast radius across security operations. While the upgrade is planned, Managed Detection & Response (MDR) can monitor for the privileged, post-exploitation activity this kind of access enables, and Implementation & Assessment Services can harden the Splunk SOAR deployment and audit the roles that make the exploit possible.

Affected and fixed versions

ProductAffectedFixed in
Splunk SOAR– < 8.8.08.8.0

References

Sources: the CVE record (MITRE), NVD, CISA KEV and SSVC, ENISA EUVD, FIRST EPSS and the vendor's own advisory. Scores and dates are shown as those sources publish them.

Written with AI assistance from the sources above and checked automatically against them before publication.