Splunk says a user whose role has all four Playbooks permissions, view, edit, execute and delete, could cause existing cross-repository references to run attacker-controlled playbook code.Splunk assigns CVSS 3.1 9.6 and classifies the flaw as incorrect authorization (CWE-863). The advisory describes an authenticated, privileged role; it does not describe unauthenticated code execution. This distinction matters when reviewing which accounts could reach the vulnerable workflow.
What it allows
How Does CVE-2026-131287 Change Playbook Execution?
Splunk describes a binding problem with existing cross-repository playbook references. If a deleted repository name is reused, Splunk SOAR can bind those references to a different source control repository. A user with the four specified Playbooks permissions could then make the references run attacker-controlled playbook code.
The advisory titles this flaw remote code execution through the REST API. Its description ties the outcome to repository name reuse and existing references, rather than to a generic API call that any account can make. This is our reading of Splunk's stated chain; the advisory does not provide an exploit sequence.
During triage, use a Vulnerability Intelligence platform to record the affected deployment and its patch status. The product version and account permissions determine the immediate work. Our SOAR glossary explains the automation context.
What Should Defenders Review?
Inventory accounts and service identities that hold all four Playbooks permissions. Review recent repository deletions, name reuse and changes to cross-repository playbook references on affected installations. These are defensive investigation steps inferred from Splunk's mechanism, not vendor-supplied indicators of exploitation.
Correlate any unexpected repository change with playbook execution and administrative audit records. An unusual change by itself does not establish exploitation of this CVE. Splunk supplies no workaround in the advisory, so an access review should support, not replace, the version upgrade.
Who is affected
Which Splunk SOAR Versions Are Affected?
Splunk lists Splunk SOAR versions below 8.8.0 as affected and 8.8.0 as the fix version. The advisory does not list a separate platform or deployment-mode exception for this CVE. Check the running version of each installation against that boundary.
Prioritize systems where users or service identities have Playbooks view, edit, execute and delete permissions together. Then examine repositories and cross-repository playbook references that those identities can manage. The role condition narrows the described attack path but does not remove the need to patch an affected version.
Upgrade Splunk SOAR to 8.8.0 or higher, as the vendor directs, and verify the running version after the change. Record the result in a vulnerability prioritization workflow so affected instances and privileged identities remain visible until verified. Splunk lists no mitigation or workaround for this entry.
Timeline
- 2026-11-18
Splunk published SVD-2026-1108 and identified Splunk SOAR 8.8.0 as the fix version.
What to do
-
Inventory Splunk SOAR installations
Identify running versions below 8.8.0 and record each instance's owner and upgrade path. Use Splunk's product-status table as the version boundary.
-
Review Playbooks permissions
Find roles and service identities with view, edit, execute and delete permissions together. Prioritize those accounts on affected instances.
-
Upgrade and verify
Upgrade Splunk SOAR to version 8.8.0 or higher. Confirm the running version after the change and retain the verification record.
-
Investigate repository changes
Review repository deletions, reused names, cross-repository references and related playbook runs. Correlate anomalies with audit records before drawing an exploitation conclusion.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-131287 in Brandefense Atlas
The Atlas record of CVE-2026-131287: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-131287 require an authenticated account?
Splunk describes a user whose role has Playbooks view, edit, execute and delete permissions. Its CVSS 3.1 vector also assigns low required privileges.
Is this the Splunk SOAR App Wizard flaw?
No. CVE-2026-131253 concerns the App Wizard and different permissions. CVE-2026-131287 concerns cross-repository playbook references after a repository name is reused.
Which version fixes CVE-2026-131287?
Splunk identifies 8.8.0 as the fix version and directs users to upgrade Splunk SOAR to 8.8.0 or higher.
Can permission changes replace the upgrade?
Splunk lists no workaround for this CVE. Reviewing powerful Playbooks roles can reduce exposure during triage, but the vendor directs users to upgrade.