Skip to main content
Menu
CVEs

Splunk SOAR remote code execution in App Wizard

Only affects Splunk SOAR below 8.8.0, and only for accounts holding Apps edit, Containers edit, and Playbooks execute permissions. Fixed in 8.8.0.

CVE-2026-131253EUVD-2026-130649Published November 19, 2026, updated

9.9CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 8.8.0
Who is exposed
Specific setups only

Summary

Written by a model

In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the Apps edit, Containers edit, and Playbooks execute permissions could use the App Wizard to execute arbitrary code as the user account that runs Splunk SOAR. This could compromise the confidentiality, integrity, and availability of the Splunk SOAR instance. The vulnerability exists because the App Wizard does not validate user-supplied identifiers before incorporating them into generated connector code.

Who should check

Teams running on-premises Splunk SOAR below 8.8.0 where users hold roles with Apps edit, Containers edit, and Playbooks execute permissions.

“In Splunk SOAR versions below 8.8.0”

advisory.splunk.com

What to do

  1. Check whether your setup matches what the bug needs.

    Splunk SOAR below 8.8.0 Attacker's account holds a role with Apps edit, Containers edit, and Playbooks execute permissions
  2. Upgrade to a fixed version: 8.8.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131253 (Remote Code Execution (RCE) through the App Wizard in Splunk SOAR), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131253 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk SOAR: fixed in 8.8.0
Fixed versions: 8.8.0.
Conditions (all must be true for the bug to be hit):
- Splunk SOAR below 8.8.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
- Attacker's account holds a role with Apps edit, Containers edit, and Playbooks execute permissions (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131253 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131253 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1108
- https://www.cve.org/CVERecord?id=CVE-2026-131253
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131253
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131253"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.9, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. cve.now early warning

    Splunk patches nearly 140 flaws across Enterprise, Enterprise Security and SOAR

  2. CVE published
  3. First seen by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  5. Posted on X by cve.now
  6. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1108
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131253
RecordNVD · CVE-2026-131253

Questions about CVE-2026-131253

Is CVE-2026-131253 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The App Wizard in Splunk SOAR can be used to run arbitrary code as the operating system user account that runs Splunk SOAR. That gives control over the confidentiality, integrity and availability of the instance.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131253?

Splunk SOAR: before 8.8.0.

Source: cve.now feed data

Am I affected, and how do I check?

Splunk SOAR versions below 8.8.0 are affected, and only when the account involved holds a role with Apps edit, Containers edit, and Playbooks execute permissions. Check your version against the Splunk SOAR version shown in the product, and review which roles hold those three permissions.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131253?

Upgrade Splunk SOAR to version 8.8.0 or higher.

Source: advisory.splunk.com, cve.org

No corrections so far. Something wrong on this page? Report an error.