In Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete
Source GCVE Database
Not known to be exploited · CVSS 9.6 Critical : upgrade to 8.8.0 as a priority.
Data as of 19 Nov 2026, 22:21 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 9.6 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Splunk SOAR to 8.8.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk SOAR | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict roles with Playbooks view, edit, execute, and delete permissions to trusted users only and monitor repository management practices to avoid reuse of deleted repository names.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with roles granting Playbooks view, edit, execute, and delete permissions can cause cross-repository playbook references to execute attacker-controlled code. This occurs because the system allows binding of existing cross-repository playbook references to a different source control repository if a deleted repository name is reused.