Act nowDisclosed

Advisory · CVE-2026-131287

Splunk SOAR cross-repository playbook references can run attacker code

A user with playbook permissions can make existing cross-repository playbook references execute attacker-controlled playbook code when a deleted repository name is reused.

Vendor
Splunk
Product
Splunk SOAR
Identifier / CWE
CVE-2026-131287
CWE-863
Action timing
Immediate
ELI5

Explain it like I’m five

Playbooks can point at code stored in another repository. If a repository is deleted and someone recreates it with the same name, old playbook links silently point at the new owner's code, and SOAR runs it.

SIMPLIFIED_ATTACK_PATH04 STEPS
  1. 01Playbook permissions

    An attacker holds a role with Playbooks view, edit, execute, and delete permissions.

  2. 02Repository name reused

    A deleted source control repository name is reused, and Splunk SOAR binds existing cross-repository playbook references to the new repository.

  3. 03Reference redirected

    Existing playbook references now resolve to attacker-controlled playbook code.

  4. 04Attacker code runs

    The referenced playbook code executes inside SOAR's automation, with its access and integrations.

What happened

Splunk disclosed CVE-2026-131287 in advisory SVD-2026-1108 on November 19, 2026. Splunk SOAR versions below 8.8.0 are affected, and the fix is version 8.8.0. The vulnerability scores 9.6 CVSS (CWE-863, incorrect authorization).

A user that holds a role with the Playbooks view, edit, execute, and delete permissions can cause existing cross-repository playbook references to run attacker-controlled playbook code. Splunk SOAR can bind existing cross-repository playbook references to a different source control repository when a deleted repository name is reused.

What to do

  1. Upgrade Splunk SOAR to version 8.8.0 or higher.
  2. Audit cross-repository playbook references and the source control repositories they resolve to, especially any repository that was deleted and recreated.
  3. Review who holds Playbooks edit, execute, and delete permissions and trim them to the minimum needed.
  4. Check playbook run history for executions of unexpected or recently changed playbook code.

Management note

This flaw turns a routine repository rename into a trust problem: playbooks that used to be safe can silently start running someone else’s code. The fix is a patch, but the durable lesson is to treat playbook source repositories as a trust boundary and watch for deletes and recreations.