In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers could import a
Source GCVE Database
Not known to be exploited · CVSS 4.3 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 | 4.3 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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
If you cannot patch yet, restrict permissions to view and edit containers to trusted users only to reduce risk.
Description
In Splunk SOAR versions below 8.8.0, an authenticated user with permissions to view and edit containers can import a container archive that causes artifacts to appear linked to cases or notes incorrectly. This occurs because the import process accepts artifact workflow state from the archive rather than deriving it from actual case associations and notes. This discrepancy can lead REST API clients and filters to use inaccurate artifact states.