In Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks could cause automation
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:21 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
Since the vulnerability affects versions below 8.8.0, upgrading to version 8.8.0 or later is implied as a remediation step. Until an official fix is confirmed, restrict playbook editing and execution permissions to trusted users only to reduce risk.
Description
Splunk SOAR versions prior to 8.8.0 contain a vulnerability where an authenticated user with permissions to edit and run playbooks can disrupt automation batches for other events. This occurs because the playbook API requests are not properly bound to the server-provided execution context, allowing interference with concurrent automation processes.