Skip to content

CVE-2026-131287

Splunk SOAR cross-repository playbook reference flaw lets users with playbook permissions run code (CVE-2026-131287)

Critical 9.6 Vendor: Cisco Published

Splunk SOAR before 8.8.0 lets a low-privileged user with playbook view, edit, execute and delete permissions run attacker-controlled playbook code through reused repository names. Fixed in Splunk SOAR 8.8.0; upgrade affected deployments.

What happened

Splunk SOAR versions before 8.8.0 allow an authenticated user whose role includes the Playbooks view, edit, execute and delete permissions to cause existing cross-repository playbook references to run attacker-controlled playbook code. The flaw exists because SOAR can bind an existing cross-repository playbook reference to a different source control repository when a deleted repository name is reused. An attacker who recreates that repository name can redirect the reference to code they control and trigger execution through the SOAR REST API.

The CVSS 3.1 score is 9.6, critical, from a network attack vector, low privileges and no user interaction; the impact is high integrity and high availability across a changed scope, with no confidentiality impact. No exploitation or public disclosure is recorded for this CVE.

Who is affected

Splunk SOAR versions before 8.8.0 are affected. The CVE record names only Splunk SOAR, so anyone operating an instance below that release should assume it applies. The fixed version is Splunk SOAR 8.8.0.

What to do now

  1. Upgrade affected Splunk SOAR deployments to 8.8.0.
  2. Until the upgrade is complete, restrict network access to the SOAR REST API so only trusted administrative systems can reach it.
  3. Review every account holding the Playbooks view, edit, execute and delete permissions and remove those rights from users who do not need them.
  4. Check source control repository configurations for re-used repository names and for cross-repository playbook references that do not belong to your normal change process.

Splunk's advisory does not list a workaround, so access reduction and prompt patching are the main controls.

How to detect it

Review source control repository configurations for deleted repository names that have been recreated and for cross-repository playbook references that have changed without an approved change. In the SOAR execution history, look for playbook runs initiated by accounts that do not normally exercise the Playbooks execute permission or that occur outside normal change windows.

Beyond the patch

A compromised SOAR instance can act on every integration it orchestrates, so code execution may quickly become lateral movement or destructive response actions. Managed Detection & Response (MDR) is the right control for that phase: EDR and SIEM telemetry can catch the post-exploitation trail after playbook code runs. If SOAR is supplied or operated by a partner, its patch latency belongs on your third-party risk register, not in a one-off fix queue; Supply Chain Defense & Third-Party Risk tracks which suppliers' software you run and how quickly they publish fixes.

Affected and fixed versions

ProductAffectedFixed in
Splunk SOAR– < 8.8.08.8.0

References

Sources: the CVE record (MITRE), NVD, CISA KEV and SSVC, ENISA EUVD, FIRST EPSS and the vendor's own advisory. Scores and dates are shown as those sources publish them.

Written with AI assistance from the sources above and checked automatically against them before publication.