In Splunk SOAR versions below 8.8.0, a user that holds a role with permission to edit playbooks and repositories could
Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:22 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.3 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:LExploitation 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
Since this affects versions below 8.8.0, upgrading to version 8.8.0 or later is implied as a remediation step. Until then, restrict roles that allow editing playbooks and repositories to trusted users only, and carefully review playbook changes. Monitor vendor advisories for official patches or updates.
Description
In Splunk SOAR versions below 8.8.0, users with roles permitting playbook and repository edits can insert modified utility blocks into playbooks. When another user with permission to edit playbook code opens and saves such a playbook, subsequent runs may issue REST API delete requests to unintended resources if the running user has delete permissions. This occurs because Splunk SOAR does not restrict utility blocks from altering REST API request paths.