External risk intelligence

Splunk SOAR Cross-Repository Playbook Reference Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-131287

Splunk SOAR is typically deployed in internal, secure network segments to manage security operations and orchestration. While it may be network-reachable, it is generally not exposed directly to the public internet, and the vulnerability requires an existing authenticated user with specific permissions to exploit, further restricting the likelihood of external exploitation.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Splunk SOAR that could allow an authenticated user with specific permissions to execute malicious playbook code. This occurs when a deleted repository name is reused, causing playbook references to bind to an attacker-controlled source repository. The core issue is that a user with certain privileges could indirectly run unauthorized code by manipulating playbook references and repository names.

  • Unauthorized code execution via playbook manipulation.
  • Matters due to potential for internal system compromise.
  • Confirm relevance and impact within your Splunk SOAR environment.

Attack Path

How an attacker could exploit the issue

An attacker with specific permissions in Splunk SOAR could trigger the execution of malicious code by exploiting how the system handles playbook references when repository names are reused. This happens because the platform might incorrectly associate existing playbook links with a new repository, allowing an attacker to inject their own commands when those playbooks are run. The vulnerability could lead to the execution of attacker-controlled code.

  • Authenticated user with specific permissions required.
  • Reusing a deleted repository name triggers the vulnerability.
  • Risk of running attacker-controlled playbook code.

Live Threat

Current exploitation, exposure, and threat context

A user with specific permissions in Splunk SOAR could manipulate playbook references, leading to the execution of unauthorized code when a deleted repository name is reused. This could impact the integrity and availability of automated security workflows.

  • Playbook execution and integrity.
  • Reusing deleted repository names.
  • Compromised automation and service disruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for Splunk SOAR, including security operations and platform engineering, must identify all instances of the affected technology. The first practical step is to confirm the reachability and business criticality of each instance to prioritize remediation efforts and identify the accountable owner before planning the update or mitigation.

  • Own by Splunk SOAR platform team.
  • Verify playbook repository configurations.
  • Plan remediation based on risk exposure.

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. It allows security teams to automate complex tasks, manage incident workflows, and integrate various security tools into a centralized environment, acting as the connective tissue for automated threat detection and response operations.

How does CVE-2026-131287 work?

This vulnerability is an incorrect authorization issue, categorized as CWE-863. It occurs because the system fails to properly validate the association between playbook references and their intended source control repository. When a deleted repository name is reused, the system can mistakenly link existing playbook references to a new, unauthorized repository, allowing an attacker to substitute legitimate playbook code with their own.

Do I need to worry if I am not reusing repository names?

The vulnerability is triggered specifically through the reuse of a deleted repository name while holding certain permissions. It is not triggered by standard, everyday playbook execution that maintains consistent repository associations. Therefore, if your organization does not perform repository deletion and recreation, the specific condition required to manipulate these references is not met.

Is my Splunk SOAR instance at risk?

According to Halo Surface Signal, Splunk SOAR is typically deployed in internal, restricted network segments rather than on the public internet. While the threat involves an attacker manipulating code, the requirement for an already authenticated user with high-level playbook permissions significantly limits the scope, making external, unauthenticated exploitation unlikely.

How should I respond to this vulnerability?

Start by identifying all instances of Splunk SOAR within your environment and verifying their current repository configurations. Ensure that you are aware of which users have playbook management permissions and audit any practices involving the deletion and reuse of repository names. Coordinate with your platform engineering team to prioritize updates for any systems that manage critical security automation workflows.

References