In Splunk SOAR versions below 8.8.0, a user with permission to create containers on one label could use the
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:35 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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
Upgrade to Splunk SOAR version 8.8.0 or later, where this vulnerability is addressed. Until upgraded, restrict container creation permissions carefully to minimize exposure.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to create containers on one label can create a container referencing a parent container they cannot access. This allows alteration of incident lineage across authorization boundaries and identification of restricted containers. The issue arises because the REST API accepts a user-supplied parent container without verifying access permissions to that container.