In Splunk SOAR versions below 8.8.0, a user with the containers:edit permission could import a container that includes
Source GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 22:35 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 8.7 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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
If you cannot patch yet, restrict containers:edit permission to trusted users only and avoid importing containers from untrusted sources to mitigate risk.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with containers:edit permission can import a container with a malicious HTML note. When another user views this note, unauthorized JavaScript may execute in their browser, potentially exposing data and allowing actions with that user's privileges. This occurs because HTML note content is not sanitized during import before rendering in Mission Control.