CVE-2026-131287 is a critical (CVSS 9.6) authorization flaw in Splunk SOAR versions below 8.8.0: when a deleted source control repository's name is reused, existing cross-repository playbook references can end up running attacker-controlled playbook code.
What Is It
CVE-2026-131287 is an incorrect authorization weakness (CWE-863) in Splunk SOAR. Splunk SOAR can bind existing cross-repository playbook references to a different source control repository when the name of a deleted repository is reused. A user whose role has the Playbooks view, edit, execute and delete permissions can use this behavior. Existing playbook references that point across repositories would then run playbook code that the attacker controls.
The record was published on 2026-11-19 by [email protected]. Its NVD status is "Received."
Why It Matters
The CNA gives it a CVSS 3.1 score of 9.6 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H:
- Network-reachable and low attack complexity
- Low privileges required: the attacker needs a role with Playbooks view/edit/execute/delete permissions
- No user interaction is required
- Scope changed, with high integrity and availability impact. No confidentiality impact is scored.
SOAR playbooks run automated response actions. If legitimate references silently point to attacker code, that code runs inside trusted automation workflows.
CISA's SSVC assessment (Coordinator role, 2026-11-19) rates exploitation as "none", automatable as "no" and technical impact as "total." The CISA KEV entry supplied for this CVE is empty, so KEV does not confirm active exploitation at this time.
What's Vulnerable
- Vendor: Splunk
- Product: Splunk SOAR
- Affected versions: all versions below 8.8.0
No CPE entries are listed in the NVD record yet.
Patch Status
The affected range ends below 8.8.0, which means Splunk SOAR 8.8.0 and later are not listed as affected. The supplied KEV data has no CISA required action or due date. Administrators should check the Splunk advisory (SVD-2026-1108) for official fix and mitigation guidance. Until they upgrade, they should review which users hold the full set of Playbooks view, edit, execute and delete permissions.