External risk intelligence

Splunk SOAR App Wizard Arbitrary Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-131253

The vulnerability affects Splunk SOAR, a security orchestration platform that is typically deployed within internal security operation centers or management networks. While it is network-reachable, it is generally not designed to be exposed directly to the public internet, making public exposure possible in some configurations but not a default or standard deployment pattern.

Code Injection

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in Splunk SOAR, a platform used for security operations. The issue allows authenticated users with specific roles to potentially execute arbitrary code, which could compromise the confidentiality, integrity, and availability of the Splunk SOAR instance. The vulnerability stems from inadequate validation of user inputs within the App Wizard feature.

  • Authorized users can run unauthorized code.
  • A compromised security platform poses significant risk.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with existing access to Splunk SOAR and specific user privileges could leverage the App Wizard feature to run arbitrary commands on the system. This is possible because the App Wizard does not properly check user input before using it to create connector code, allowing malicious code to be injected and executed with the privileges of the Splunk SOAR service account. Such a compromise could impact the confidentiality, integrity, and availability of the entire Splunk SOAR instance.

  • Authenticated user with specific permissions required.
  • App Wizard feature allows arbitrary code execution.
  • Compromise of instance confidentiality, integrity, and availability.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an authenticated user with specific permissions could leverage the App Wizard in Splunk SOAR to run arbitrary code. This could impact the confidentiality, integrity, and availability of the Splunk SOAR instance, as the App Wizard fails to validate user-provided identifiers before using them in connector code.

  • Splunk SOAR instance data and services.
  • Malicious code execution via App Wizard.
  • Compromise of confidentiality, integrity, availability.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Splunk SOAR requires immediate attention from teams managing security orchestration and automation platforms, likely including Security Operations (SecOps) and potentially Infrastructure or Platform Engineering. The first practical step is to identify all Splunk SOAR instances, confirm their network exposure and business criticality, and then engage the accountable owner to plan remediation based on risk.

  • Identify and engage Splunk SOAR owners.
  • Verify instance exposure and criticality.
  • Plan risk-based remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Splunk SOAR?

Splunk SOAR is a security orchestration, automation, and response platform. Security teams use it to streamline incident response by automating repetitive tasks, integrating various security tools, and managing workflows across the security operations center.

What does CVE-2026-131253 mean?

This vulnerability is classified as Improper Control of Generation of Code (CWE-94). It means the App Wizard feature fails to sanitize user-provided identifiers before inserting them into generated code. Consequently, the system treats this untrusted input as executable instructions, leading to arbitrary code execution.

How can an attacker trigger this bug?

An attacker needs an authenticated user account that already possesses specific permissions: Apps edit, Containers edit, and Playbooks execute. Simply visiting the interface is insufficient; the attacker must actively use the App Wizard feature to inject malicious identifiers that the system then incorrectly processes as code.

Is my Splunk SOAR instance at risk?

According to Halo Surface Signal, Splunk SOAR is typically deployed within protected internal networks. While the vulnerability is technically network-reachable, direct exposure to the public internet is not a standard configuration, which may limit the attack surface for most organizations.

What should I do to address this issue?

Begin by auditing your infrastructure to locate all active Splunk SOAR instances. Verify their network placement and criticality to the business. Finally, coordinate with the designated platform owners to prioritize remediation steps, starting with an upgrade to version 8.8.0 or higher.

References