In Splunk SOAR versions below 8.8.0, a user with permission to view and edit containers and at least one container
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
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 permissions to view and edit containers and container labels to trusted users only. Monitor vendor advisories for official fixes.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permissions to view and edit containers and at least one container label can set misleading user and app provenance on containers they create. This occurs because the REST API accepts client-supplied values for server-managed container fields, allowing the user to also infer the existence of user IDs and installed app identifiers.