On this page (7 sections)
A critical vulnerability, CVE-2026-131253, affects Splunk SOAR versions below 8.8.0. An authenticated user whose role combines a few specific permissions can abuse the App Wizard to run arbitrary code as the account that runs Splunk SOAR. The GitHub Advisory Database entry shows a CVSS score of 9.9, though that entry is marked Unreviewed.
If you run Splunk SOAR for security automation, especially with many analysts or shared roles, this is worth reviewing today. The flaw is not exploitable by anonymous visitors, but a single over-privileged or compromised account could be enough.
What happened
The CVE was published on November 19, 2026, with a vendor advisory identified as SVD-2026-1108. According to the NVD record, the issue lets an authenticated user execute arbitrary code as the user account that runs Splunk SOAR. The description says this could compromise the confidentiality, integrity and availability of the instance.
Only one independent publisher covers this story so far. The NVD text repeats the GitHub advisory wording, so the two should not be read as separate confirmations. The 9.9 score and the vector come from the GitHub Advisory Database page, which labels the entry Unreviewed; the NVD text in our research does not show a score. We could not review the Splunk advisory text itself, so check it directly for the authoritative severity, fixed version and any workaround.
Technical details
The App Wizard in Splunk SOAR helps users create connector apps. Per the advisory, it does not validate user-supplied identifiers before incorporating them into generated connector code. In other words, text a user types as a name or identifier can end up inside code that the system then generates.
This is the weakness class CWE-94. It is similar to injection bugs elsewhere: when an application builds code from input without neutralizing special characters, the input can change what the code does. Here the resulting code runs as the account that runs Splunk SOAR, so the impact depends on what that account can reach on your host and network.
The CVSS vector in the GitHub entry lists network attack vector, low complexity, low privileges, no user interaction and a changed scope, with high impact on confidentiality, integrity and availability. In CVSS terms, a changed scope means the impact may extend beyond the vulnerable component itself.
Who is affected
Any Splunk SOAR deployment running a version below 8.8.0 is in scope. Exploitation requires an authenticated user whose role holds all three of these permissions:
- Apps edit
- Containers edit
- Playbooks execute
That narrows the exposure to accounts with those rights, but it should not be assumed to be a small group without checking. Roles in automation platforms are sometimes created broadly so analysts can build and run playbooks. If one such account is phished or its password is reused elsewhere, a permissions question could become a server compromise.
How to check your exposure
- Find your Splunk SOAR version in the product's administration or about information and compare it with 8.8.0. Anything below it is affected.
- List the roles in your instance and note which ones include Apps edit, Containers edit and Playbooks execute together.
- List the users and service accounts assigned to those roles, including API or automation accounts, and confirm each one is still needed.
- Check whether those accounts use strong, unique passwords and multi-factor or single sign-on where your deployment supports it.
- Review recent App Wizard activity and newly created or modified apps for anything nobody on your team recognizes.
What to do now
- Read Splunk advisory SVD-2026-1108 and confirm the fixed version, the severity rating and any vendor guidance.
- Plan an upgrade of Splunk SOAR to 8.8.0 or later, following Splunk's upgrade documentation, and test it first on a non-production instance if you have one.
- Until you upgrade, reduce the number of users holding Apps edit, Containers edit and Playbooks execute together, following least privilege.
- Reset passwords and review sessions for accounts that hold those permissions if you see anything unusual.
- Restrict network access to the SOAR web interface to trusted networks or a VPN where practical.
- Run the SOAR service account with the minimum operating system privileges it needs, so code running as that account can reach less.
- Rotate credentials stored in or used by SOAR integrations if you suspect an account was misused.
Detection and monitoring
The sources do not describe indicators of compromise, so treat the following as general good practice rather than confirmed signatures of this flaw. Watch for unexpected new or changed apps and connectors, unusual use of the App Wizard, and playbook runs started by accounts that do not normally run them. On the host, look for unfamiliar child processes or outbound connections from the account that runs Splunk SOAR.
Forward SOAR audit logs to a system outside the platform so they survive a compromise of the instance. If your SOAR web interface is reachable from the internet, a security scan of the hosts you verify can help you see what is exposed, and certificate and header-change monitoring can flag unexpected changes on public endpoints. These help with visibility only and do not detect or fix this specific flaw.
For broader guidance on responding to a suspected intrusion, see website hacked: what to do.
What we do not know yet
- No public exploitation has been reported in the research, and the CVE is not in the CISA KEV catalog at the time of writing.
- The GitHub entry is marked Unreviewed and lists affected and patched versions as unknown in its structured fields; the version range comes from the description text.
- The CVSS 9.9 score and vector are shown on the GitHub Advisory Database page; we could not confirm them against the Splunk advisory.
- No exploit details, indicators or workarounds are described in the sources.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
