In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission and restricted
Source GCVE Database
Not known to be exploited · CVSS 7.2 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 22:39 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.2 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation 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. Since this is an on-premises product, administrators must apply the update manually. No alternative mitigations are specified in the advisory.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with System Settings edit permission and restricted tenant access can modify settings of tenants outside their scope via the REST API. This flaw arises because the Tenant REST API verifies the edit permission but fails to enforce tenant restrictions, allowing unauthorized access to tenant configurations. Exploitation could lead to exposure of confidential tenant data, unauthorized changes to tenant settings and automation, or disruption of tenant operations.