Splunk SOAR code execution via argument injection in app installer
Only affects Splunk SOAR below 8.8.0, where a user with only the apps:edit role can install a connector app. Fixed in 8.8.0.
- 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, a user that holds a role with only the apps:edit permission could install a connector app that causes Splunk SOAR to write attacker-controlled files outside the app directory. This could let the user modify files used by Splunk SOAR and execute arbitrary code as the user account that runs Splunk SOAR. The vulnerability is possible because Splunk SOAR constructs the dependency installation command from app-supplied metadata without preventing that metadata from changing its arguments. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (help.splunk.com/
Who should check
Teams running on-premises Splunk SOAR below 8.8.0 where users hold roles with the apps:edit permission, such as those who install connector apps.
“Splunk SOAR 8.8 Below 8.8.0 8.8.0”
What to do
Check whether your setup matches what the bug needs.
Splunk SOAR below 8.8.0 User holds a role with the apps:edit permissionUpgrade 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-131263 (Argument Injection during App Installation 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-131263 (entry last updated 2026-11-20):
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)
- User holds a role with the apps:edit permission (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-131263 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131263 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
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-131263
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-131263"}.Affected versions
- Splunk Splunk SOARfixed in 8.8.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, 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
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1108 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131263 |
| Record | NVD · CVE-2026-131263 |
Questions about CVE-2026-131263
Is CVE-2026-131263 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?
A user who holds only the apps:edit permission can install a connector app in a way that writes attacker-controlled files outside the app directory. The same flaw lets that user modify files Splunk SOAR uses and run arbitrary code as the account that runs Splunk SOAR.
Source: advisory.splunk.com
Which versions are affected by CVE-2026-131263?
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 the issue needs a role with the apps:edit permission. To check a setup, look at the installed Splunk SOAR version and at which roles hold apps:edit.
Source: advisory.splunk.com
How do I fix CVE-2026-131263?
Upgrade Splunk SOAR to 8.8.0 or later, which is the fixed version listed for this vulnerability.
Source: advisory.splunk.com
Related
- CVE-2026-131287Remote Code Execution (RCE) through the REST API in Splunk SOAR
- CVE-2026-131295Improper Authorization in Playbook Execution in Splunk SOAR
- CVE-2026-131293Improper Access Control in the Data Management Automation API in Splunk SOAR
- CVE-2026-131297Single Sign-On Authentication Bypass in Splunk SOAR
- CVE-2026-131282Information Exposure through the REST API in Splunk SOAR
- CVE-2026-131288[Flashpoint] Privilege Escalation through HAProxy Cluster Operations in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.