In Splunk SOAR versions below 8.8.0, a Splunk SOAR user who can edit and run playbooks for a permitted container label
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:22 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:H/A:NExploitation 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 recommended if such a version exists. Otherwise, monitor vendor advisories for official fixes. Restricting user permissions to the minimum necessary may reduce exposure.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to edit and run playbooks for a specific container label can manipulate playbook automation for containers they are not authorized to view. This occurs because the Playbook Automation API does not verify that a supplied playbook run identifier is bound to the correct execution context. Exploitation requires an existing running playbook on a container label outside the user's permitted view.