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

Splunk SOAR App Wizard Code Execution (CVE-2026-131253)

CVE-2026-131253 is a code injection vulnerability in the App Wizard of Splunk SOAR before version 8.8.0.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-131253
Vendor
Splunk
Affected Product
Splunk SOAR
Exploitation
Not confirmed
Published
2026-11-18

Splunk says an authenticated user with Apps edit, Containers edit, and Playbooks execute permissions could run arbitrary code as the account running Splunk SOAR.Splunk published the advisory on November 18, 2026, and rates the flaw Critical at CVSS 3.1 9.9. The stated impact covers the confidentiality, integrity, and availability of the SOAR instance. These required permissions are central to triage: the advisory does not describe an unauthenticated attack.

What it allows

How Does CVE-2026-131253 Reach Code Execution?

Splunk says the App Wizard incorporates user-supplied identifiers into generated connector code without validating them. A user holding all three named permissions could use that path to execute arbitrary code as the Splunk SOAR service account.

The affected boundary is therefore the application's code-generation process and the privileges of its runtime account. This is our reading of Splunk's description, not a disclosed exploit procedure. See the remote code execution glossary for the distinction between code execution and broader system control.

What Is Known About Exploitation?

Splunk's advisory describes the attack conditions and impact, but does not document an exploitation incident. CVE-2026-131253 was absent from CISA's Known Exploited Vulnerabilities catalog version 2026.11.18. Neither statement establishes whether a particular deployment has been attacked.

For prioritization, record the installed version and the roles that combine the three required permissions in a Vulnerability Intelligence platform workflow. Review unexpected App Wizard activity on affected servers as a local investigation step. Splunk has not published a detection signature in this advisory.

Who is affected

Which Splunk SOAR Versions Are Affected?

Splunk lists Splunk SOAR versions below 8.8.0 as affected and 8.8.0 as the fixed version. Its product table gives one version boundary, with no separate operating-system or deployment-mode rows. Inventory self-managed SOAR instances and verify the version actually running on each server.

Exposure also depends on an authenticated account having Apps edit, Containers edit, and Playbooks execute permissions together. Review role assignments for that combination, including roles granted to automation or service users. A version inventory alone does not establish whether the required permissions exist.

How Should Administrators Verify the Fix?

Splunk's stated solution is to upgrade to Splunk SOAR 8.8.0 or higher. After deployment, confirm the running version on every SOAR server and retain the result in the patch management process.

Splunk lists no mitigation or workaround for this CVE. While scheduling the upgrade, review who has the three required permissions and investigate unexpected App Wizard use. These are defensive checks we recommend, not substitutes for Splunk's fix or proof of exploitation.

Timeline

  1. 2026-11-18

    Splunk published SVD-2026-1108 and identified Splunk SOAR 8.8.0 as the fix for CVE-2026-131253.

What to do

  1. Inventory Splunk SOAR versions

    Identify self-managed Splunk SOAR servers running a version below 8.8.0. Record the version reported by each running instance.

  2. Review the required role combination

    Find accounts and roles with Apps edit, Containers edit, and Playbooks execute permissions together. Prioritize affected instances where that combination is present.

  3. Upgrade and verify

    Upgrade affected Splunk SOAR servers to 8.8.0 or higher. Confirm the running version after the change on every server.

  4. Review App Wizard activity

    Investigate unexpected App Wizard use on affected instances using available local audit records. This is a defensive review suggestion, not a vendor detection signature.

What Brandefense can do

Frequently Asked Questions

Does CVE-2026-131253 require authentication?

Yes. Splunk says the user must be authenticated and hold Apps edit, Containers edit, and Playbooks execute permissions.

Which version fixes CVE-2026-131253?

Splunk identifies version 8.8.0 as the fix. Upgrade earlier Splunk SOAR versions and verify the version running after deployment.

What privileges would the code run with?

Splunk says the code could execute as the user account that runs Splunk SOAR. The advisory does not say this grants root privileges.

Is active exploitation established?

The Splunk advisory does not document an incident. The CVE was absent from CISA's KEV catalog version 2026.11.18; these are evidence limits, not an incident assessment.

Sources

  1. Security Vulnerabilities in Splunk SOAR - November 2026Splunk
  2. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
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 →