On this page (7 sections)

CVE-2026-131287 is a critical flaw in Splunk SOAR versions below 8.8.0. According to the GitHub Advisory Database entry, a user whose role holds the Playbooks view, edit, execute and delete permissions could make existing cross-repository playbook references run attacker-controlled playbook code.

If you operate a SOAR platform, especially one connected to external source control repositories for playbooks, you should check your version and review who holds that permission set. The vendor advisory is SVD-2026-1108.

What happened

The advisory was published on November 19, 2026. The description says Splunk SOAR can bind existing cross-repository playbook references to a different source control repository when a deleted repository name is reused. A playbook that referenced a repository by name could therefore end up pointing at a different repository carrying the same name, and run whatever playbook code that repository contains.

The sources available so far trace back to a single origin. The NVD entry repeats the same description and is not separate confirmation. The GitHub entry is marked unreviewed and lists affected and patched versions as unknown, so the version boundary comes from the description text itself.

Technical details in plain terms

The weakness class is incorrect authorization (CWE-863): the product performs a check, but not correctly. Here, the trust placed in a reference to a repository appears to be tied to its name rather than to the specific repository that was originally approved. If a repository is deleted and a new one is created under the same name, existing references can silently follow the name to the new source.

The CVSS vector reads as network-reachable, low complexity, low privileges required, no user interaction, with a changed scope. Impact is rated high for integrity and availability and none for confidentiality. A changed scope generally means the impact extends beyond the component that is vulnerable, which fits playbook code running outside the boundary of the permissions the user was meant to have.

The sources do not describe a proof of concept, and this article does not include exploitation steps. Details beyond the advisory text are unconfirmed.

Who is realistically exposed

Exploitation requires an authenticated account, so this is not an anonymous internet attack on its own. The advisory names the needed role: Playbooks view, edit, execute and delete permissions together. Exposure is highest in these situations:

  • Splunk SOAR is below 8.8.0.
  • Playbooks use cross-repository references to external source control repositories.
  • Several people, contractors or service accounts hold roles with all four playbook permissions.
  • Repositories are deleted and recreated, so names get reused.

A compromised or malicious account matching that role could be enough, which is why credential hygiene around SOAR users matters here.

How to check your exposure

Start with the product version, shown in the SOAR web interface under its About or version information. The sources do not give a command for this, so use the interface or your deployment documentation. Then review roles and repositories:

  1. Record the installed Splunk SOAR version and compare it with 8.8.0.
  2. List every role that includes Playbooks view, edit, execute and delete, and list the users and service accounts assigned to them.
  3. List configured source control repositories and note any that were deleted and recreated under the same name.
  4. Review recent playbook changes and executions for playbooks you do not recognize, especially cross-repository ones.

What to do now

Caution. Upgrading a SOAR platform can interrupt automation and running playbooks. Back up first, follow Splunk's upgrade documentation, and schedule a maintenance window.
  1. Read the vendor advisory SVD-2026-1108 and confirm the fixed version for your deployment.
  2. Upgrade Splunk SOAR to 8.8.0 or later.
  3. Until you can upgrade, reduce the number of accounts holding the full playbook permission set to those who need it.
  4. Avoid deleting and recreating repositories under the same name, and review existing cross-repository references for the correct source.
  5. Check playbook content and recent execution history for unexpected code, and rotate credentials stored in or used by affected playbooks if anything looks wrong.
  6. Enforce strong authentication for all SOAR accounts and remove dormant ones.
Tip. Treat the playbook delete permission as sensitive. In this flaw it is part of the combination that makes the reference rebinding possible.

Detection and monitoring afterwards

Keep audit logs for playbook edits, repository configuration changes and role assignments, and alert on changes to repositories that playbooks depend on. Watch for playbook runs that start new outbound connections or touch assets they normally do not. Since SOAR often holds credentials for other systems, a suspected abuse should be handled as a possible credential exposure for connected tools.

For broader habits that apply to any administrative platform, see our guide to small business website security and the latest items on the Webforta blog. If you run public websites alongside these tools, Webforta Monitor can alert on certificate, DNS and header changes, though it does not cover internal SOAR platforms.

Timeline

Known dates
DateEvent
2026-11-19CVE-2026-131287 published by NVD and added to the GitHub Advisory Database; Splunk advisory SVD-2026-1108 referenced

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-131287 - GitHub Advisory Databasegithub.com
  2. CVE-2026-131287: In Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete permissions could cause existing…nvd.nist.gov ·
  • Splunk SOAR
  • CVE-2026-131287
  • Incorrect authorization
  • Playbooks
  • Patch now