In Splunk SOAR versions below 8.8.0, a user that holds a role with the containers:view permission could access
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:40 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 on-premises versions below 8.8.0, upgrading to version 8.8.0 or later is implied as a remediation step. Until then, restrict the assignment of the containers:view permission to trusted roles only. Review and enforce strict role and tenant scope configurations to limit unauthorized access.
Description
In Splunk SOAR versions below 8.8.0, users with a role granting the containers:view permission could access automation history for containers beyond their assigned label or tenant scope. This exposure includes action parameters, connector result summaries, and other investigation and response activities. The issue arises because the REST API checks container view permissions but does not enforce scope restrictions on automation history access.