CVE-2026-131253: Splunk SOAR Code Execution
Standard scheduled maintenance window.
TL;DR - CVE-2026-131253 is a critical authenticated arbitrary-code-execution flaw in Splunk SOAR’s App Wizard. - Splunk SOAR versions below 8.8.0 are affected. - Exploitation requires Apps edit, Containers edit, and Playbooks execute permissions. - No public PoC or confirmed in-the-wild exploitation was identified. Upgrade to 8.8.0 or later promptly.
CVE-2026-131253 is a critical Splunk SOAR vulnerability affecting versions below 8.8.0. A sufficiently privileged authenticated user can abuse the App Wizard to execute arbitrary code as the account running the Splunk SOAR service. Organizations should prioritize upgrading affected deployments, reviewing privileged roles, and investigating unexpected connector, application, or playbook activity.
For background, see our overview of privileged access management and CVE remediation guidance.
What Is the Root Cause?
The root cause is insufficient validation of user-supplied identifiers before the Splunk SOAR App Wizard incorporates those identifiers into generated connector code. A sufficiently privileged user can influence the generated code instead of being limited to safe, validated identifiers and expected connector structures.
This design issue turns an administrative or developer-oriented workflow into a code-execution boundary. The generated connector code executes as the operating-system account running Splunk SOAR. Its ultimate impact depends on that account’s permissions, accessible files, network access, secrets, and relationships with other SOAR components.
Organizations should not assume that the application role limits the impact to Splunk SOAR objects. If the service account can read configuration files, access credentials, call internal APIs, or reach sensitive network segments, successful exploitation could extend beyond the SOAR user interface.
Technical Notes
The available advisory material does not provide a safe proof-of-concept payload, vulnerable code fragment, or detailed parser behavior. Defenders should avoid attempting to reproduce the exploit in production.
Affected version: < 8.8.0
Feature: App Wizard
Required role permissions:
- Apps edit
- Containers edit
- Playbooks execute
Outcome: arbitrary code execution as the Splunk SOAR service account
What Happened?
According to the NVD description, an authenticated user with a specific combination of permissions can use the Splunk SOAR App Wizard to execute arbitrary code. The resulting impact may include compromise of the SOAR instance’s confidentiality, integrity, and availability.
| Field | Details |
|---|---|
| CVE ID | CVE-2026-131253 |
| Product | Splunk SOAR |
| CVSS v3.1 base score | 9.9 Critical |
| CVSS vector | Not provided in the retrieved authoritative record; do not infer one |
| Attack vector | Remote through the Splunk SOAR application using the App Wizard |
| Authentication | Required |
| Required privileges | Apps edit, Containers edit, and Playbooks execute |
| Affected versions | Splunk SOAR below 8.8.0 |
| Fixed version | Splunk SOAR 8.8.0 |
| Patch available | Yes |
| CISA KEV status | Not listed as of 2026-11-19 |
This is not an unauthenticated, internet-wide exploit. However, the required permissions are powerful and may be assigned to users who build integrations, manage containers, or execute playbooks. If such an account is compromised or misused, the vulnerability can provide a path from application-level access to code execution under the SOAR service account.
Technical Notes
The relevant execution path involves the App Wizard’s generation of connector code. Exploitation depends on an authenticated account that can access the affected functionality and has all three permissions:
Apps edit
Containers edit
Playbooks execute
Analyst’s Take: The permission combination is the key exposure question, but it does not eliminate the need to patch. A compromised account with those permissions can cross from SOAR administration into code execution as the service account, so version inventory and role review should happen together.
Who Needs to Act?
Organizations running Splunk SOAR versions below 8.8.0 need to act. Splunk identifies version 8.8.0 as the fixed release.
| Product | Affected versions | Fixed version |
|---|---|---|
| Splunk SOAR | Below 8.8.0 | 8.8.0 |
The affected population includes self-managed Splunk SOAR deployments and any operational environment where administrators have not confirmed the deployed release. Treat any Splunk SOAR instance below 8.8.0 as affected until its version is verified and upgraded.
Identify users who simultaneously hold Apps edit, Containers edit, and Playbooks execute permissions. Remove unnecessary permissions, separate duties where practical, and check whether service accounts or shared administrative accounts possess this combination.
Permission reduction is not a substitute for patching because compromised privileged accounts may still exploit the feature before access is revoked.
Technical Notes
Collect the installed Splunk SOAR version using approved administration and inventory procedures. The research note does not provide a vendor-specific version-reporting command, so do not assume that a generic Splunk Enterprise command applies to SOAR.
Vulnerable: Splunk SOAR < 8.8.0
Fixed: Splunk SOAR >= 8.8.0
Why Is the CVSS Score Critical?
The NVD record reports a CVSS v3.1 base score of 9.9, categorized as Critical. Splunk’s advisory also identifies 9.9 as the advisory’s highest score. The retrieved NVD record did not include the CVSS vector for this specific CVE, so the vector’s individual values cannot be responsibly reconstructed.
The score is consistent with a vulnerability that can produce high confidentiality, integrity, and availability impact and that requires only an authenticated account with a defined set of powerful permissions. The exploit does not require an unauthenticated attacker, but successful execution provides arbitrary code under the SOAR service account.
| CVSS-related factor | Confirmed information |
|---|---|
| Base score | 9.9 |
| CVSS version | 3.1 |
| Vector string | Not available in the retrieved record |
| Authentication or user access | Authenticated user required |
| Privilege condition | Apps edit, Containers edit, and Playbooks execute required |
| Confidentiality, integrity, availability impact | Described as potentially compromised |
Administrators should not lower their response priority because the vector is unavailable. The score and technical description are sufficient to prioritize remediation, while the permission prerequisites should guide exposure analysis and monitoring.
Has CVE-2026-131253 Been Exploited?
No authoritative evidence of exploitation in the wild was identified in the retrieved NVD, Splunk advisory, CISA KEV lookup, or associated research results. CVE-2026-131253 is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
A public proof of concept was also not identified. The current status is therefore:
Confirmed in-the-wild exploitation: Not identified in retrieved sources
Public PoC: Not identified in retrieved sources
CISA KEV listing: Not listed as of 2026-11-19
These statements reflect the sources checked and do not guarantee that exploitation has never occurred. A privately held exploit, unreported incident, or later publication would not appear in the current assessment.
The absence of a KEV entry should not be interpreted as evidence that the vulnerability is low risk. The combination of code execution, a critical score, and a role set that may exist in security operations environments makes this a high-priority patching issue even without observed exploitation.
Detection Guidance
Detection should answer two questions:
- Which Splunk SOAR instances are exposed?
- Have privileged users recently performed suspicious App Wizard, connector-generation, or playbook activity?
Version inventory identifies vulnerable deployments. Identity and application telemetry can help identify attempted or successful misuse.
Review audit data for activity by accounts holding all three required permissions. Look for unexpected creation or modification of connectors, applications, containers, and playbooks; unusual activity outside normal change windows; newly created administrative or service accounts; and process or network behavior originating from the Splunk SOAR service account.
Because the available advisory does not publish exploit-specific log strings, defenders should not rely on a single signature.
SIEM Hunting Template
The following query provides a starting point for hunting in Splunk SOAR audit data. Field names vary by deployment, so adapt it to the available audit schema:
index=soar_audit
| eval actor=coalesce(user, username, actor)
| search action IN ("app_wizard", "connector_create", "connector_update",
"app_create", "app_update", "playbook_execute")
| stats values(action) as actions
values(object) as objects
min(_time) as first_seen
max(_time) as last_seen
count
by actor src_ip
| where mvcount(actions) > 0
Use this as a hunting template rather than a confirmed vendor detection. Investigate events that meet one or more of these conditions:
- Actor has Apps edit, Containers edit, and Playbooks execute
- App Wizard activity is new or unusual for the actor
- Connector or application changes occur outside approved change windows
- Activity originates from a new source address or unfamiliar administrator workstation
- The SOAR service account launches unexpected child processes
- The service account makes unusual outbound connections after an App Wizard change
If host telemetry is available, correlate suspicious App Wizard activity with process creation, file writes, authentication events, and outbound network connections for the SOAR service account. The research does not provide a confirmed network signature, so behavioral correlation is more defensible than inventing a payload-based signature.
Remediation and Patching
Upgrade Splunk SOAR to 8.8.0 or later. This is the vendor-specified fix and the only confirmed version boundary in the available material.
Follow the organization’s normal backup, change-control, compatibility-testing, and rollback procedures. After the change, verify that the running version on each node or deployment component is at least 8.8.0.
Recheck user roles because permission cleanup remains valuable even after patching.
No workaround was identified in the retrieved Splunk advisory. If an immediate upgrade is not possible:
- Restrict access to the Splunk SOAR management interface.
- Remove the three-permission combination from users who do not need it.
- Suspend unnecessary App Wizard use.
- Increase monitoring of application, connector, container, and playbook changes.
These are compensating controls, not a vendor-confirmed fix.
Upgrade Checklist
Pre-change check: Splunk SOAR < 8.8.0
Upgrade target: Splunk SOAR 8.8.0 or later
Post-change check: Confirm installed and running version >= 8.8.0
The supplied research does not include a verified package-manager, installer, or orchestration command for Splunk SOAR. Do not use an unverified command in production. Instead, use the organization’s approved Splunk SOAR upgrade procedure and record the resulting version.
Until the upgrade is complete:
1. Identify users with Apps edit + Containers edit + Playbooks execute.
2. Remove any unnecessary permission from those accounts.
3. Restrict management access to trusted administrative networks.
4. Disable or limit App Wizard use where operationally feasible.
5. Monitor connector, application, container, and playbook changes.
6. Investigate unexpected service-account process or network activity.
If compromise is suspected, preserve SOAR audit logs and host telemetry, rotate credentials accessible to the SOAR service account, review newly created or modified connectors and playbooks, and assess downstream systems that the service account could access. Coordinate incident response with the team responsible for the SOAR deployment and consult the vendor advisory for current product-specific guidance.
References
-
Splunk Security Advisory SVD-2026-1108
Vendor advisory containing the affected range, fixed version, severity information, and remediation guidance. -
NVD record for CVE-2026-131253
Vulnerability record describing the App Wizard code-execution issue and required permissions. -
CISA Known Exploited Vulnerabilities Catalog
The CVE was not listed in the catalog at the time of assessment on 2026-11-19. Non-inclusion does not prove that exploitation has never occurred.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.