In Splunk SOAR versions below 8.8.0, a user with edit permission for a container or workbook task could store
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:34 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
A fix is available in Splunk SOAR version 8.8.0 and later. Users should upgrade to version 8.8.0 or above to remediate this vulnerability. No vendor advisory or patch link was provided in the input, but the fixed version is explicitly stated. Until upgraded, restrict edit permissions to trusted users and avoid viewing notes from untrusted sources.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with edit permissions on container or workbook tasks can inject attacker-controlled HTML into notes. When viewed by users with view permissions, this can lead to execution of unauthorized JavaScript in their browsers, potentially exposing data and allowing actions via the authenticated session. This occurs because active content is not properly neutralized before rendering in Mission Control.