In Splunk SOAR versions below 8.8.0, a user that holds a role with the Assets edit or delete permission and access to
Source GCVE Database
Not known to be exploited · CVSS 8.8 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.8 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/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
Upgrade to Splunk SOAR version 8.8.0 or later, where this vulnerability is addressed. Since the affected versions are below 8.8.0 and the vendor documentation indicates the issue is fixed in 8.8.0, applying this official fix is the recommended remediation. No alternative mitigations are indicated in the advisory.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with roles permitting asset editing or deletion and access to one or more tenants can modify or delete assets assigned to other tenants via the REST API. This occurs because the system verifies permissions but does not confirm tenant access for the target asset. Exploitation could lead to redirection of connector traffic, exposure of credentials and operational data, and disruption of integrations and data ingestion for other tenants.